GuidesAPI ReferenceMCPChangelog
Shared

Customise one template slot (admin, paid)

put/api/notification-templates

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".

Authorization

sessionCookie
sb-qxrvgfkjyvbngipqvslu-auth-token<token>

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

application/json

curl -X PUT "https://example.com/api/notification-templates" \  -H "Content-Type: application/json" \  -d '{    "type": "confirmation",    "channel": "email",    "body": "string"  }'
{  "ok": true}

Revert one template slot to the default (admin) DELETE

Deletes the override row. Deliberately NOT plan-gated: an org that has downgraded must always be able to get back to the stock templates.

Upload the organization logo (admin, or manage_org_settings) POST

Fixed 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).