ads
GET /v1/ads/shield/exclusions
The IP and placement exclusions the shield asked Google for.
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/shield/exclusions \
-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 (docs/1006 §15, SHIELD2). Per campaign, the suspected sources ranked by measured cost are kept inside Google's 500-per-campaign IP cap (the customer's own exclusions count against it); a source that ever converted is never excluded. Every exclusion is an ad-account change: approve-first unless exclusions is automatic, with its 30-day Undo. Never on the platform's own account.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
org_id (query) | string | No | — |
status (query) | string<queued, applied, rejected, removed, undone, failed> | No | — |
before (query) | string | No | — |
limit (query) | integer | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsShieldExclusion[] | Yes | — |
next_before | object | Yes | — |
per_campaign_cap | integer | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429