Remove a campaign photo (admin, or manage_org_settings)
/api/marketing/campaigns/{id}/photoDeletes the object and nulls photo_url. Draft-only. 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
Path Parameters
Campaign id.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/marketing/campaigns/string/photo"{ "ok": true}Upload a campaign photo (admin, or manage_org_settings) POST
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.
Live "will reach N" count for a segment or tag GET
The compose screen's live audience preview, debounced against IN-MEMORY form state rather than the saved draft: it has to answer before autosave persists. `{id}` is not read; kept only for URL consistency with the rest of this feature's nested routes, since the count depends purely on company + kind + value. The emailable/consent filter (applyMarketingAudienceFilter, migration 0143) is always applied on top, same as the clients page's own `emailable` chip.