ads

GET /v1/ads/network-notices

The ad-network changes that affect this organisation's accounts (za-195).

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.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

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 GET https://api.zinndigital.com/v1/ads/network-notices \
  -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. Each item is one staff-curated vendor change (dated, with the vendor's own source page) matched against one connection by the daily audit: which campaigns or ad groups it affects, what to do, and the pending safe fix (change_id) where one exists. Acknowledged notices are not listed.

Parameters

NameTypeRequiredWhat it is
org_id (query)stringNo—

Response

NameTypeRequiredWhat it is
dataAdsNoticeMatch[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429