Stay organized with collections
Save and categorize content based on your preferences.
This section specifies the feed files used to transmit your inventory data to
Ordering Redirect. The contents of your feeds defines which services you are
providing, what services are available, and when the services are available. The
structure of the inventory feeds are defined by the Google Maps Booking API. The
following feeds are mandatory for the Ordering Redirect integration:
Merchants feed: Contains data describing your merchants.
Services feed: Describes the services provided by your merchants.
Some fields in these feeds are required and some are optional. Any field marked
as optional can be left out of the feed when empty.
The feeds format is described using protocol buffer 3 syntax. You have the
option to upload the feeds file as a binary serialization of the protocol buffer
data in pb3 format or in a derived JSON format.
We recommend uploading the feeds in JSON format.
This guide is specific to the Ordering Redirect protocol buffers. For general
information on how to use the protocol buffers to generate a pb3 file,
here is an example in Java.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-10 UTC."],[[["Integrations with the Actions Center utilize Feeds, the Maps Booking API, and a Booking Server to manage and update inventory data."],["Feeds, in JSON or pb3 format, transmit inventory data to the Actions Center, encompassing merchant details, services offered, and availability."],["The Maps Booking API enables real-time updates and booking cancellations, primarily for end-to-end integrations."],["A Booking Server is essential for the Actions Center to handle bookings on your behalf, utilizing a REST-based API for new integrations."],["Starter integrations primarily rely on Feeds for data updates and may omit the Maps Booking API and Booking Server components."]]],["The Actions Center integration relies on three main components: Feeds, Maps Booking API, and Booking Server. Feeds, in JSON or pb3 format, transmit inventory data, including merchants, services, and availability, via SFTP upload. The Maps Booking API updates information between feed submissions and manages bookings; REST calls are used for this. The booking server is required for creating bookings. Three main feeds are mandatory: Merchants, Services, and Availability. All feeds must be uploaded in the format `PROCESS_AS_COMPLETE`.\n"]]