ads
DELETE /v1/ads/connections/{connection_id}/rules/{rule_id}
Delete a rule and its schedule (za-196).
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}/rules/{rule_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.rule_delete. The rule stops and its schedule is removed; its run log and the changes it made stay, each with its own 30-day Undo.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
rule_id (path) | string | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 429