Create an experience
/api/experiencesAdds a special night, set menu or ticketed event to the catalog. company_id comes from the verified JWT claim, never the body.
Authorization
sessionCookie 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
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/experiences" \ -H "Content-Type: application/json" \ -d '{ "name": "string" }'{ "experience": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08" }}Update a reservation PATCH
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.
Update an experience, or archive/restore it PATCH
Two shapes in one route, same posture PATCH /api/products/{id} takes. A body of exactly `{"archived": true|false}` sets/clears `archived_at` and returns immediately, no other field required. Any other body is a full replacement of the catalog fields (parseExperienceInput's contract). RLS scopes the update, so an id from another org matches zero rows and returns 404.