Message the venue
/api/book/{slug}/manage/{token}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.
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 booking's manage token.
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
curl -X POST "https://example.com/api/book/string/manage/string" \ -H "Content-Type: application/json" \ -d '{ "message": "string" }'{ "ok": true}Leave the walk-in lineDELETE
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.
Change a booking, or its dietary preferences and occasionPATCH
A guest moves their own booking to another time. One endpoint for both engines: a manage link points at a booking, not at a product, so the engine is worked out from the booking and the caller does not choose. Only the time changes: same service, same staff member, same party size. That is what lets a guest reschedule go through without staff review. The new time must respect the venue's notice period too, so a guest cannot sidestep the cutoff by moving to a slot an hour from now. The slot is re-derived server-side, and a booking the venue cancelled mid-flow is not brought back.