ads

POST /v1/ads/connections/{connection_id}/matching-pages/{page_id}/approve

Approve and publish the page, then switch the ad group's final URL (za-N6).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

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}/approve \
  -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. Approve-first: nothing is published before this. A Temporal workflow writes the page into the site's document root, waits until it answers 200, and only then switches the ad group's final URL through the metered gate, as an Undo-able change. 422 landingNotInGoodStanding when the organisation is not in good standing.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—
page_id (path)stringYes—

Response

NameTypeRequiredWhat it is
dataAdsMatchingPageYesOne 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