ads
GET /v1/ads/connections/{connection_id}/matching-pages
Matching landing pages — the connection's pages and candidate ad groups (za-N6).
Authentication
Send an API key as a bearer token. The key must carry the ads.view 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 GET https://api.zinndigital.com/v1/ads/connections/{connection_id}/matching-pages \
-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.view. Every open page of the connection (a candidate ad group found by the scan, a page being written, ready to preview, publishing, live or being unpublished) and the 20 most recent closed ones. Read from our own rows — never a network call (docs/1006 §94). alternatives_only=true keeps only competitor alternative pages (za-109, a non-empty rival), as the MCP ads_matching_pages tool does.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
alternatives_only (query) | boolean | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | object | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 429