Save the floor's shared note for a date
/api/hospitality/floor/service-notesUpserts through book_upsert_service_note() rather than PostgREST's own upsert(), because the one-day-note/one-service-note invariant is two PARTIAL unique indexes with different predicates, not one plain unique constraint on_conflict's column list could target. companyId and updatedBy are derived server-side from the caller's own session, never taken as request fields.
An empty string is how a note is cleared; there is no DELETE.
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 PUT "https://example.com/api/hospitality/floor/service-notes" \ -H "Content-Type: application/json" \ -d '{ "date": "string" }'{ "note": "string", "updatedByEmail": "string", "updatedAt": "2019-08-24T14:15:22Z"}Read the floor's shared note for a date GET
The day's shared, guest-hidden note about running the floor (migration 0230): one row per company+date when `servicePeriodId` is omitted, or one specific service's own note alongside it when given. Every member reads the same row; "private" means hidden from guests and the public booking page, not from teammates. Returns an empty note, never a 404, when nothing has been written yet; the absence of a note is not an error.
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.