Leave the walk-in line
/api/book/{slug}/walkin/{token}The guest's own cancel, by the token from joining. Allowed while waiting or after the table was called; everyone behind them moves up one.
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.
The status token returned when joining the walk-in line.
Response Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/book/string/walkin/string"{ "ok": true}Place in the walk-in lineGET
One guest's status, by the token from joining. The token is the whole credential; an unknown one is a 404. `state` is `waiting` (with `position`, 1 is next, and `quotedMinutes` when the host quoted a wait), `ready` (come to the host stand), `seated`, `left` or `closed`. The status page polls this about every 20 seconds while visible.
Message the venuePOST
Allowed regardless of the change cutoff and on any status, unlike PATCH and DELETE. "I am running late" and "why was this cancelled" are exactly the moments someone needs to reach a venue; refusing them because the booking is two hours away would be backwards. A manage link is public to anyone holding it, so there is a flood cap: 20 guest messages per booking, after which the guest is told to contact the venue directly. That is a cheap guard, not real rate limiting; there is none anywhere in this API yet.