GuidesAPI ReferenceMCPChangelog
Appointments engine

Remove a service image

delete/api/services/{id}/image

Deletes the stored object and nulls image_url. Storage removal is best-effort and its failure does not fail the request.

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

Path Parameters

id*string

Service id.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/api/services/string/image"
{  "ok": true}

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.

Create a service group POST

A named shelf services hang off on the public page (migration 0054); "Hair Colouring", "Mens Cuts"; with an optional photo and colour. New groups land at the end of the order (`sort_order = max+1`). Busts the cached public booking config.