Feed overview

This section specifies the feed files used to transmit your inventory data to Reserve with Google. The contents of your feeds defines which services you are providing, what services are available, and when the services are available.

Follow the starter integration guide or the end-to-end integration guide (depending on the type of your integration) 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:

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 optional feeds are also specified:

  • Conversion feed: Describes conversion metrics that were generated by your partnership with Reserve with Google.

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.

We recommend using gzip to compress feeds prior to upload.

This guide is specific to the Reserve with Google protocol buffers. For general information on how to use the protocol buffers to generate a pb3 file, here is an example in Java.