References Overview

This section gives more details about the 3 main pieces of an integration with Reserve with Google. You will use each of these in the steps outlined in the End-to-End guide.


Feeds are files in JSON or pb3 format used to transmits your inventory data to Reserve with Google. This allows you to submit all of your data at once to update the merchants, services, and availability slots using an SFTP upload.

Maps Booking API

The Maps Booking API allows you to update objects in the Reserve with Google system between feed submissions to keep availability up to date. The API also allows you to cancel bookings that are made through Reserve with Google.

There are two ways to access the API. The first way is through RPC calls and the second way is by using REST calls.

Booking Server

In order for Reserve with Google to create bookings on your behalf, you must set up a Booking server.


The v3 version is the latest version of the API, and supports a REST-based interface. All new integrations should use the v3 API.


There are two versions of the gRPC server specification. The v2 version is the last released version of gRPC interface. The v0 version is for partners who were already in the process of integrating using the legacy v0 specification.