ads
POST /v1/ads/connections/{connection_id}/matching-pages/{page_id}/unpublish
Undo — put the old final URL back, then remove the page (za-N6).
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}/matching-pages/{page_id}/unpublish \
-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-logged. The final-URL change is undone first (or a waiting one rejected); only then is the page's folder removed, so no ad points at a missing page.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
page_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsMatchingPage | Yes | One matching landing page for one ad group on a site hosted with us (za-N6, docs/1006 §94). |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429