The Reservations API allows you to create and manage reservations at restaurants.
This API provides all the necessary functionality to move a reservation through the phases of its lifecycle, such as from the reservation request until completion.
The Reservations API works together with the Reservation Locations API, which provides information about the physical location of a restaurant, as well as that restaurant’s availability and reservation conditions.
The Reservations API also works together with the Time Slots API, which allows you to retrieve availability information about time slots at a restaurant on a specific date and for a specific party size.
With the Reservations API, you can:
It’s important to note the following points before starting to code:
The following methods have different permission requirements depending on the fields specified, and the value of certain fields.
Create Reservation
requires additional permissions when the following fields are specified:
status
source
reservation.details.tableIds
reservation.details.endDate
ignoreReservationLocationConflicts
ignoreTableCombinationConflicts
These additional permission requirements are as follows:
MANAGE RESERVATIONS (FULL)
permission scope.If a source
is not specified, the value assigned to it depends on the permissions of the identity making the call:
MANAGE RESERVATIONS (FULL)
permission scope, source
is set to UNDEFINED
. Otherwise, source
is set to ONLINE
.source
is set to ONLINE
.source
is set to UNDEFINED
. Otherwise, source
is set to ONLINE
.Calling Get Reservation with fieldsets
set to FULL
requires additional permissions:
FULL
fieldset requires either the MANAGE RESERVATIONS (MEDIUM)
or MANAGE RESERVATIONS (FULL)
permission scope.FULL
fieldset requires API key authorization with appropriate permissions.FULL
fieldset requires elevated permissions.For a comprehensive glossary of Table Reservations terms, see Terminology.