ads
DELETE /v1/ads/connections/{connection_id}/allowed-terms/{allowance_id}
Withdraw an allowance; the name is refused in that group again (audited).
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.
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 DELETE https://api.zinndigital.com/v1/ads/connections/{connection_id}/allowed-terms/{allowance_id} \
-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.manage. Audit action ads.allowed_term_remove. The gates refuse the name in that group at their next call. Undo is allowing it again (POST). An allowance of another account is 404 (noSuchAllowance).
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
allowance_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsAllowedTerm | Yes | One competitor name allowed in ONE ad group's ad text (za-237, docs/1006 §53). |
Errors this endpoint can return
401 · 403 · 404 · 429