List bookable table slots
The hospitality availability grid. Live holds count as busy on purpose: a hold blocks its table exactly as a confirmed booking does until it expires.
tableId is deliberately not returned: it would leak the floor plan, and a client-held allocation goes stale the moment someone else books, so the hold POST picks the table server-side regardless. GET .../table-options is the one opt-in exception, for venues with tablePickerEnabled on.
area_id/level_id narrow the candidate tables before allocating; a level_id includes every area nested under it.
Ranged mode (days). Same contract as the appointments grid: the single-date shape ({slots, reason}) stays the default, and days greater than 1 switches the response to {days: {"<date>": {slots, reason}, ...}}.
Path Parameters
The organization's public booking slug, i.e. the {slug} in /{slug}. Only orgs with status active resolve; anything else is a 404.
Query Parameters
YYYY-MM-DD, strictly. A non-matching string is a 400, not a coerced date. The first day answered in ranged mode.
dateCapped at 30: party size is attacker-controlled and feeds a slot loop.
1 <= value <= 30Narrows to one room. Mutually exclusive with level_id; sending both is a 400.
uuidNarrows to one floor, INCLUSIVE of every room nested under it. Mutually exclusive with area_id; sending both is a 400.
uuidScopes the grid to one published Experience: a dated Experience answers ONLY on its own event date (every other date returns reason: "closed"), an Experience restricted to specific service periods is narrowed to them, and one with its own party bounds is validated against party_size (400 if outside them) and its own capacity_per_sitting, if set, independently of the venue-wide maxOnlinePartySize. A 404 if the id does not resolve to a published Experience for this business.
uuidHow many consecutive days from date to answer in one call. Omitted or 1 keeps the original single-date {slots, reason} shape; 2 to 14 switches the response to {days: {"<date>": {slots, reason}, ...}}.
1 <= value <= 14Present only when the guest manage page calls this route to pick a new time for an existing booking. See the appointments twin's identical parameter for the full reasoning.
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/book/string/reservations/availability?date=2019-08-24&party_size=1"{ "slots": [ { "startsAt": "2019-08-24T14:15:22Z" } ], "reason": "full", "banner": "string", "notices": { "property1": { "dateNote": "string", "closedReason": "string" }, "property2": { "dateNote": "string", "closedReason": "string" } }}Join today's walk-in linePOST
A guest at the door (a QR code) or on a booking page where today is full puts themselves in the venue's walk-in line for **today**, on the venue's own clock, and gets a status token back. Only while the venue is open, and only when it has switched the online line on. The guest lands in the same line the host works from, first come first served. The response carries the status token once; it is also emailed with a link to the status page. Email is required (the status link and the "table ready" notice go there); phone follows the venue's own booking form rule. A party above the venue's `maxOnlinePartySize` is refused. Rate limited per visitor before the slug is resolved or the body is parsed.
Same time at sister venuesGET
When the time a guest wanted is gone, the booking page's alternatives panel asks this for the SAME organization's other table-reservation venues that have a table at that exact time for that party. Answers an empty list unless the organization switched sister-venue suggestions on in its business settings (off by default). Each candidate is checked through `GET .../reservations/availability` itself, called in process, so a venue listed here is one whose own checkout will accept that sitting. Only active venues, never an API sandbox, never one whose online booking is paused by the booking meter. At most six are checked (name order) and three listed. Each entry carries the venue's name, slug, the time and a link to its booking page with `date`, `time` and `party_size` prefilled; nothing else about a sister venue is returned. Rate limited on the guest `read` budget before the slug is resolved; each candidate check spends one more unit of it. Uncached, like availability.