Join today's walk-in line
/api/book/{slug}/walkinA 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.
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.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/book/string/walkin" \ -H "Content-Type: application/json" \ -d '{ "name": "string", "email": "user@example.com", "partySize": 1 }'{ "ok": true, "token": "string"}Join the waitlistPOST
What a guest leaves when a date came back with **no tables at all**. The entry lands on the venue's reservations screen. **Nothing is held or promised by joining.** The venue offers a table later if one frees up, and the guest books it through the ordinary flow; whoever gets there first gets it. Rate limited per visitor before the slug is resolved or the body is parsed, so it cannot be used to probe which venues exist. A party above the venue's `maxOnlinePartySize` is refused with `enquiryRequired`: send a group enquiry instead.
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}, ...}}`.