ads

POST /v1/ads/zaraz/zones

The Cloudflare zones a pasted Zaraz token can reach (the zone picker).

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.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

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/zaraz/zones \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "token": <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

za-131 (docs/1006 §88). Gated on ads.manage. The customer's scoped Cloudflare API token (Zone Read + Zaraz Edit) is used for this one call and NOT stored; it is never echoed back. Every page of zones is read. A refusal carries refusal.adsconnect.zaraz.<code>: tokenShape, tokenRejected, rateLimited, unavailable (Cloudflare answered 5xx), unexpected (our side failed or Cloudflare's answer was not understood; names no vendor).

Request body

NameTypeRequiredWhat it is
org_idstringNo—
tokenstringYes—

Response

NameTypeRequiredWhat it is
dataAdsZarazZone[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429