Introduction to Waitlists

Waitlist partners must complete the End-to-end Integration Guide. Certain steps in the end-to-end guide are not necessary. The guidelines on this page explain what steps apply to partners interested in using the waitlist feature on Reserve with Google. Please read through this overview before going through the integration steps.

Launch process

The diagram below outlines the process to launch your waitlist enabled merchants on Reserve with Google.

Figure 1: High level integration steps

Overall, the major data flows between you (Partner) and Google are captured in diagram below:

Figure 2: Integration data flow diagram

Guidelines for all waitlist partners

  • The service for every waitlist merchant must have waitlist_rules populated.

  • Waitlist only merchants do not need to have availability feeds provided to Reserve with Google.

  • The partner's booking server must implement all the methods listed in the E2E guide section 5b. Implement Booking server: API (you) - Waitlist-based Booking. Hybrid partners that support both reservations and waitlists can add on the new methods to their existing booking server.

  • Reserve with Google will go through a similar set of tests for the waitlist methods in the booking server. These tests are outlined below in this document.

  • Reserve with Google is actively developing the API testing tools and sandbox front end for Waitlist merchants. The API testing tools, sandbox, and skeleton servers mentioned in the guide currently only cover reservations.

Guidelines for waitlist only partners

Waitlist partner test cases

Google will test the following use cases to ensure the functionality of the waitlist methods in your Booking server implementation. We will also test and monitor latency. All of these tests must pass prior to Step 8.

WaitEstimate retrieval test cases

  • Wait estimates are returned for each party size requested in a BatchGetWaitEstimatesRequest

Waitlist entry creation test cases

  • A waitlist entry can be created from a CreateWaitlistEntry request
  • Business logic errors show up in the response if waitlist entry creation fails
  • If a CreateWaitlistEntry attempt succeeds, the same response is returned when the same CreateWaitlistEntry is received again
  • If a CreateWaitlistEntry attempt fails, retry when the same CreateWaitlistEntry is received again
  • Waitlist entries show up in the merchant's interface
  • Calls to GetWaitlistEntry successfully return the created waitlist entry

Waitlist entry deletion test cases

  • Existing waitlist entries can be deleted

Sample waitlist service feed (JSON)

Waitlist service feed