Skip to content

Cancel a booking

delete/api/book/{slug}/manage/{token}

Sets status to cancelled rather than deleting, so the venue keeps the history and the slot or table is released by exactly the rules a staff cancellation uses. Compare-and-set on the current status.

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.

token*string

The booking's manage token.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/api/book/string/manage/string"
{  "ok": true}

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.

Answer the venue's intake formPUT

The guest answers whatever questions the venue set up for this booking. Serves both engines: the token points at a booking, and the engine is worked out from it. PUT rather than POST because there is exactly one response per booking: a guest reopening their link edits their answers rather than stacking a second submission. The form is looked up server-side, not taken from the body, since the venue may have switched or retired forms since the page was drawn. A service-specific form wins over the venue-wide one, and only active forms are served. Answers are validated against it: required questions present, dropdown answers within their `options`, lengths capped. Deliberately NOT gated on the venue's guest self-service policy, unlike PATCH and DELETE: a venue that switched off guest rescheduling still asked these questions, and the hour before a visit is exactly when someone remembers their allergy.