Delete a service (admin, or manage_services)
/api/services/{id}Hard delete. The foreign key from book_appointments has no cascade on purpose, so a service with booking history cannot be deleted; deactivate it instead (active: false). Gated to admin, or a staff login granted manage_services (migration 0082): price, duration and every other service setting is a delegable business decision now.
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
Path Parameters
Service id.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/services/string"{ "ok": true}Update a service PATCH
Full replacement of the service's editable fields; despite the verb, every field in the schema is written on every call, so a partial body resets what it omits. RLS scopes the update, so an id from another org simply matches zero rows and returns 404.
Upload a service image POST
Stores the file at `{companyId}/{serviceId}` in the `service-images` bucket and writes a cache-busted public URL onto the service row. Not admin-gated: a photo is part of editing the service. Ownership is checked BEFORE the upload (one indexed lookup ahead of a multi-megabyte write), so a request naming a service the caller does not own is a 404 with nothing written; this used to be upload-first-then-sweep, and this paragraph used to describe that.