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 the Actions Center. The contents of your feeds defines
which services you are providing, what services are available, and when the
services are available.
Check the References and Samples accordion to learn how to share these feeds with us.
The structure of the inventory feeds are defined by the Google Maps Booking
API.
The following feed is mandatory across any integration:
Merchants feed: Contains data describing your merchants.
In addition, the 2 following feeds are mandatory for end-to-end integration.
Services feed: Describes the services provided by your
merchants.
Availability feed: Lists availability slots of 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 Actions Center 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 2024-10-31 UTC."],[[["Inventory data is transmitted to Actions Center using feed files, defining offered services, availability, and merchant details."],["Three mandatory feeds are used: Merchants, Services, and Availability, with the first being required for any integration, and the latter two necessary for end-to-end functionality."],["Feeds must be uploaded with the `PROCESS_AS_COMPLETE` processing instruction, and the recommended format is JSON, optionally compressed using gzip."],["The structure of these inventory feeds is based on the Google Maps Booking API and utilizes protocol buffer 3 syntax, allowing for data serialization in pb3 or JSON formats."],["Optional fields can be excluded from the feed when empty, and further details on feed sharing and protocol buffer usage can be found in the References and Samples section."]]],["Inventory data is transmitted via feeds to the Actions Center, defining service offerings and availability. A merchants feed is mandatory for all integrations. End-to-end integrations require services and availability feeds. All feeds must be uploaded with the `PROCESS_AS_COMPLETE` instruction. Feeds can be in pb3 or JSON format, with JSON being the recommendation. Optional fields can be omitted. gzip compression is advised before uploading. The feed structure is defined by the Google Maps Booking API.\n"]]