Read the floor's shared note for a date
/api/hospitality/floor/service-notesThe 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.
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
Query Parameters
YYYY-MM-DD.
^\d{4}-\d{2}-\d{2}$Omit for the day note. A specific service period id for that service's own note, offered alongside the day note.
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/hospitality/floor/service-notes?date=string"{ "note": "string", "updatedByEmail": "string", "updatedAt": "2019-08-24T14:15:22Z"}Remove an area lock (admin) DELETE
Puts the floor, room or table back on sale. Admin where creating one is staff, matching `book_tables`/`book_areas`/`book_levels`/link groups; it reads backwards until you notice which direction is dangerous: adding a lock is protective and reversible, removing one is what lets a booking land on top of the function it was holding. There is no PATCH. 0047 grants no UPDATE and writes no update policy: a lock is two instants and a subject with nothing derived from it, so "move it an hour" is a delete and an insert either way.
Save the floor's shared note for a date PUT
Upserts 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.