Shared

Upload a campaign photo (admin, or manage_org_settings)

post/api/marketing/campaigns/{id}/photo

Same upload/remove shape as POST /api/organization/logo, except the row write goes through service-role rather than the RLS-scoped client: book_campaigns has no grant to authenticated at all (see PATCH /api/marketing/campaigns/{id}'s own header). Draft-only, same as the PATCH/DELETE on the parent path.

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

Campaign id.

Request Body

multipart/form-data

The campaign 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

application/json

application/json

curl -X POST "https://example.com/api/marketing/campaigns/string/photo" \  -F file="string"
{  "ok": true,  "photoUrl": "http://example.com"}