GuidesAPI ReferenceMCPChangelog
Hospitality engine

Update a reservation

patch/api/reservations/{id}

The reservations twin of PATCH /api/appointments/{id}: partial, only present keys are written.

Deliberately NOT re-checked on edit: the table's seat range and the period's cover cap. A host seating five on a four-top is a real thing venues do and the reason a manual override screen exists. The double-booking constraint is the one rule staff cannot override, and Postgres enforces it.

Authorization

sessionCookie
sb-qxrvgfkjyvbngipqvslu-auth-token<token>

The dashboard's Supabase Auth session cookie, set at sign-in. Large sessions are split across numbered chunks (…auth-token.0, .1), so treat this as a cookie family rather than one name.

Every request re-validates it against the Auth server (getUser()), never by decoding the cookie locally: a JWT nothing has checked is not a credential. Tenancy is then read from the verified app_metadata.company_id claim and enforced by row-level security; it is never read from request input, on any route, ever.

role (admin / staff) is deliberately not in RLS. It gates specific actions in route code, the operations marked admin below, so hiding a button in the UI is cosmetic only, and a route's own check is the enforcement.

In: cookie

Path Parameters

id*string

Reservation id.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Properties1 <= properties

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PATCH "https://example.com/api/reservations/string" \  -H "Content-Type: application/json" \  -d '{}'
{  "ok": true}

Assign a table to a server for a date PUT

The whole assignment API in one verb: a `serverId` gives the table to that server for the date (upsert on the one-server-per-table-per-date key), an explicit null takes it back. Per-DATE, not per-service: sections are chalked up once for the night. No same-tenant checks in the route. Both foreign keys are composite over company_id (0011's pattern), so a cross-tenant table or server id is rejected by the database itself.

Create an experience POST

Adds a special night, set menu or ticketed event to the catalog. `company_id` comes from the verified JWT claim, never the body.