Same time at sister venues
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.
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, a real calendar date.
dateHH:MM on the venues' wall clock.
^([01]\d|2[0-3]):[0-5]\d$Party size.
1 <= value <= 30Response Body
application/json
application/json
curl -X GET "https://example.com/api/book/string/siblings?date=2019-08-24&time=string&party=1"{ "venues": [ { "name": "string", "slug": "string", "time": "string", "url": "string" } ]}List bookable table slotsGET
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}, ...}}`.
List free tables for a slotGET
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.