Upload the About section photo (admin, or manage_org_settings)
/api/organization/about-photoA 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.
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 About section photo. 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/about-photo" \ -F file="string"{ "ok": true, "aboutImageUrl": "http://example.com"}Remove the booking-page background (admin, or manage_org_settings) DELETE
Deletes the object and nulls `background_image_url`. Takes no body.
Remove the About section photo (admin, or manage_org_settings) DELETE
Deletes 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.