GET /v1/ads/connections/{connection_id}/findings

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}/findings \
  -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 detector of the audit (docs/1006 §38) writes what it finds here — never a count alone: open suggestions first (most recently seen first), then the automatic changes of the last 30 days. why is the reason the screen says in words (an empty why → the kind's own words); figures are the finding's numbers (estimates say so in estimate), never an internal resource name. Read from the rows the audit stored — never a network call in the request. At most 200.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 429