Upload the organization logo (admin, or manage_org_settings)
/api/organization/logoFixed path per company ({companyId}/logo, no extension), so a re-upload simply overwrites via upsert and there are no orphaned files to track. Busts the cached public booking config. Gated to admin, or a staff login granted manage_org_settings (migration 0082).
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
multipart/form-data
The logo. Sent as multipart/form-data under the field name file.
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/organization/logo" \ -F file="string"{ "ok": true, "logoUrl": "http://example.com"}Customise one template slot (admin, paid) PUT
Upserts one (type, channel) slot. Written with service-role because the table has no INSERT/UPDATE policy for `authenticated` at all; this route is the plan gate, so it has to be the only writer. Unknown `{{variables}}` are rejected at the write boundary rather than degrading to a blank word at render time. That is the difference between "your template is wrong" and "your guests got a broken email".
Remove the organization logo (admin, or manage_org_settings) DELETE
Deletes the object and nulls `logo_url`. Takes no body.