ads

POST /v1/ads/campaign-offerings/lookup

Which offering each of many campaigns advertises, in one call.

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.view 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/lookup \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "pairs": <object[]> }'

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.view. Up to 5,000 pairs, answered in one database query. A campaign with no offering answers offering_id: null (Unassigned). source is auto, person or launch.

Request body

NameTypeRequiredWhat it is
pairsobject[]Yes—

Response

NameTypeRequiredWhat it is
dataAdsCampaignOffering[]Yes—

Errors this endpoint can return

401 · 422 · 429