ads

GET /v1/ads/connections/{connection_id}/landing-pages

Every ad final URL's last landing-page check (LPDIAG2, za-205/za-209).

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.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}/landing-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. The daily audit renders each enabled ad's final URL once on a phone (390x844) through our own Lighthouse runner and judges it (docs/1006 §41): the status and where it redirects, the page's language and main heading, whether the call to action is in the first screen (cta_above_fold, null when the page has no button we recognise), mobile LCP and CLS, the ad groups landing there, and the problems found — each one is also a finding (GET .../findings, why lp_*) carrying its concrete fix. checked: false means the page could not be read that day (never "ok"). Read from the state the audit stored — never a network call in the request.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
checked_atstringNo—
dataAdsLandingPage[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 429