GET /v1/ads/connections/{connection_id}/ad-quality

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}/ad-quality \
  -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. Reads the account (three bounded queries) and spends nothing; the rewrite itself runs in the connection's daily audit under the customer's ads mode. limited_serving is read from what the network's API gives (ads approved-limited, a limited-serving policy topic, a first spend inside 90 days) with the brand-clarity checks and the fix list. weak_ads lists every enabled responsive search ad the network rates POOR or AVERAGE, or that a guard refuses (brand not pinned in headline 1, another company's name, "free" for a software advertiser, generic-only lines), with the rewrite's own score and its reasons when it cannot reach GOOD. Cached 10 minutes per connection; refresh=1 reads again. A Microsoft connection answers supported: false. A read that failed returns report: null with failure (a VendorFailure).

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 429