Reorder areas (rooms)
/api/areasThe body is every area in its new order, and array position IS the new sort_order (migration 0111): byte-for-byte the same shape and write pattern (a loop of individual .update({sort_order}).eq('id') calls, not a single statement) as PATCH /api/service-groups. Not admin-gated: reordering a room is not more sensitive than renaming one, the same permission level as PATCH /api/areas/{id}.
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 PATCH "https://example.com/api/areas" \ -H "Content-Type: application/json" \ -d '{ "ids": [ "6e0346a3-e54d-40e3-9779-4ba1e707e35b" ] }'{ "ok": true}Create an area (room) POST
The product's first real area-creation API; `book_areas` has existed since migration 0011, but until 0030 the only write path was assigning an EXISTING area to a table. Optionally nests under a level via `levelId`. Lands at the end of the list (`sort_order = max+1`, migration 0111) and busts the cached public booking config, matching services/groups.
Update an area PATCH
Full replacement of the area's fields, same as its table twin.