Remove the About section photo (admin, or manage_org_settings)
/api/organization/about-photoDeletes the object and nulls about_image_url. The About section falls back to its existing photo ladder (site-pages.ts's aboutPhoto()), not to the hero image. Takes no body.
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
Response Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/organization/about-photo"{ "ok": true}Upload the About section photo (admin, or manage_org_settings) POST
A second, distinct photo for the About section (migration 0131), separate from the one hero image /api/organization/background uploads, which HomeBody/AboutBody used to reuse for About too. Same shape as that route otherwise: same 5 MB ceiling and bucket (`booking-backgrounds`, a distinct fixed path per company), same admin gate.
Upload the website's own hero photo (admin, or manage_org_settings) POST
The website's OWN hero photo (migration 0194), independent of /api/organization/background's widget hero (SiteShell used to always reuse that same photo). Same shape as that route otherwise: same 5 MB ceiling and bucket (`booking-backgrounds`, a distinct fixed path per company), same admin gate. Unset falls back to the widget's own photo, live.