ads

GET /v1/ads/networks

Every ad network Zinn® Ads has a driver for (za-54).

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 GET https://api.zinndigital.com/v1/ads/networks \
  -H "Authorization: Bearer zdk_live_…"

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. Read from the one network registry (docs/1006 §66), never a call to a vendor. Each row names the network (label, a proper noun), the click id it adds to a landing URL, what the autopilot does there (capabilities[], stable codes from search_terms, keywords, negatives, bids, budgets, audiences, creatives, placements), whether its campaigns and spend are read into the stored reading (campaign_feed), whether the daily audit runs on it (audit) and whether it can be connected now (available: its app credentials are configured).

Response

NameTypeRequiredWhat it is
dataobject[]Yes—

Errors this endpoint can return

401 · 403 · 429