ads

POST `/v1/ads/connections/{connection_id}/paused-ads/delete`

Delete all paused ads of one account (ADMGMT1).

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 POST https://api.zinndigital.com/v1/ads/connections/{connection_id}/paused-ads/delete \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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.paused_ads_delete (metadata count, started). Reads the paused ads now and makes one approved delete per ad (narrowed to resources when given — the list the person saw in the preview; an ad no longer paused is left alone), each with its snapshot and Rebuild; ONE workflow sends them all. 503 when the workflow could not be started (the changes stay approved).

Parameters

Name	Type	Required	What it is
`connection_id (path)`	`string`	Yes	—

Request body

Name	Type	Required	What it is
`resources`	`string[]`	No	—

Response

Name	Type	Required	What it is
`connection_id`	`string`	Yes	—
`count`	`integer`	Yes	—
`started`	`boolean`	Yes	—
`changes`	`AdsChange[]`	Yes	—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503

POST /v1/ads/connections/{connection_id}/paused-ads/delete