Skip to content

Answer the venue's intake form

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

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.

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.

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 PUT "https://example.com/api/book/string/manage/string" \  -H "Content-Type: application/json" \  -d '{    "answers": {      "property1": "string",      "property2": "string"    }  }'
{  "ok": true}

Cancel a bookingDELETE

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.

MCP endpointPOST

The Model Context Protocol endpoint an AI assistant connects to in order to read the public booking surface on a guest's behalf. One endpoint for the whole platform, with the venue as a tool argument. **Not a REST operation.** The body is JSON-RPC 2.0 and the method vocabulary is the MCP specification's (`initialize`, `tools/list`, `tools/call`, ...). Read the MCP specification for the envelope, and call `tools/list` against this endpoint for the tools: that is the authoritative, self-describing answer. **Six tools, none of which books anything.** `find_venues` searches the businesses that chose to be found by name, suburb or postcode; `get_venue`, `find_appointment_times` and `find_table_times` read; `start_appointment_booking` and `start_table_booking` turn a slot token into a short-lived link on the venue's own booking page, where the guest enters their own details and confirms. No tool accepts a guest's name, email or phone, and none moves money. Opening a `start_table_booking` link holds that table for about ten minutes on the booking page; the tool call itself holds nothing. Everything returned is already shown to any visitor of the venue's booking page. **Findable on every plan, bookable from Growth and Pro (Venue Growth and Venue Pro).** `get_venue` answers for any venue with its `bookingPage` link. The two time searches and the two booking tools need the venue's plan to include AI booking; below it they answer with `bookingPage` and `liveTimes: false`. **No timezone and no machine-readable instant is ever returned.** Times come back as display text plus an opaque signed slot token, because a model handed a timezone next to a time converts it and books hours wrong. **No CORS.** An MCP client is a server-to-server HTTP client; the browser-based MCP Inspector cannot reach this, so use the Inspector CLI. **No authentication**, by design: nothing this endpoint reads is private.