The following describes the details of the Reserve with Google integration process that are unique to the local services vertical.
Follow the standard high-level integration process outlined in the end-to-end integration guide.
Key Local Services Guidance
The following are examples and tutorial covering features that are required by the local services integration:
Feeds: Sample Local Services Feeds
Notes: Merchants feed
categoryfield should be set to
home_servicevalue for all merchants. Services feed
home_service_datafield should be populated with the service categories shared with the partner.
Virtual Estimate: Sample Virtual Estimate Feeds
Notes: Merchants enrolled in virtual estimate services will need to send one additional service feed per service category (plumber, electrician).
typefield should be set to
direct_merchant_paymentfield should be populated.
virtual_sessionfield should be populated, including
is_session_prerecordedshould be set as false.
- Each merchant will have maximum of 1 virtual service feed for each service category(plumber, electrician). Virtual service feed will have empty job type
Notes: The following methods must be implemented:
Method Requirements BatchAvailabilityLookup Required CreateBooking Required UpdateBooking Optional (Used to modify/cancel bookings) ListBookings Optional (Used for automated testing) GetBookingStatus Optional (Used for automated testing) CheckAvailability Deprecated (Superseded by BatchAvailabilityLookup)
Real-time updates: Structuring Real-Time Updates
Optional Local Services Features
Below are a list of features that are compatible with the fitness integration. None are required by this integration, but many will be necessary to make sure Reserve with Google follows your company’s business logic when serving your inventory: