Skip to content

List free tables for a slot

GET
/api/book/{slug}/reservations/table-options

The opt-in exception to the availability grid's "no tableId" rule: given a slot the guest already has from the ordinary grid, lists the tables actually free at that instant, with name and seat count, never coordinates.

Returns 404, not 403, when tablePickerEnabled is off, checked at request time, so a venue that just switched it off stops listing table names immediately.

An instant with no matching slot (outside every period, no table fits, or inside a closure) is not an error; it returns an empty list.

Path Parameters

slug*string

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

date*string

YYYY-MM-DD, strictly.

Formatdate
party_size*integer
Range1 <= value <= 30
starts_at*string

The exact slot start the guest picked from the availability grid.

Formatdate-time
area_id?string

Same filter as the availability route. Mutually exclusive with level_id.

Formatuuid
level_id?string

Same filter as the availability route, inclusive of nested rooms. Mutually exclusive with area_id.

Formatuuid
experience_id?string

Same parameter the availability and hold requests send: narrows the slot to this published Experience's own hours and seating length instead of the venue's ordinary service periods, so table options agree with the grid that offered the slot. Not needed for an ordinary reservation.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/api/book/string/reservations/table-options?date=2019-08-24&party_size=1&starts_at=2019-08-24T14%3A15%3A22Z"
{  "tables": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "name": "string",      "seatsMin": 0,      "seatsMax": 0    }  ]}

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.

Hold a tablePOST

Takes a 10-minute hold on a table and returns its id. The guest then confirms it with PATCH once they have typed their details; that gap is exactly what the hold protects. The slot is re-derived server-side and matched exactly against the requested `startsAt`. The database's overlap guarantee, not the availability read, is what makes the allocation safe. **400 versus 409.** 400 means the request can never succeed (the time is outside every service period, no table seats a party that size, or the venue is closed); 409 means it was bookable and someone else has it. Reload the availability grid on 409 only. `areaId`/`levelId` narrow the candidate tables the same way the availability grid does. `tableId` asks for a specific one of them: honoured only if `tablePickerEnabled` is on (silently ignored otherwise, so a stale client still completes a normal booking) and only if that table is still free for this exact slot. Losing that race is a 409, not a 400: the time is still bookable, just not at that table.