ads

POST /v1/ads/campaign-offerings

Set (or clear, with no offering) which offering one campaign advertises.

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the ads.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/ads/campaign-offerings \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "connection_id": <string>, "campaign_id": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Gated on ads.manage; audit action ads.campaign_offering_set. Recorded as set by a person.

Request body

NameTypeRequiredWhat it is
connection_idstringYes—
campaign_idstringYes—
campaign_namestringNo—
offering_idstringNo—

Response

NameTypeRequiredWhat it is
connection_idstringYes—
campaign_idstringYes—
offering_idstringYes—
sourcestring<auto, person, launch>Yes—

Errors this endpoint can return

401 · 404 · 422 · 429