ads
PATCH /v1/ads/connections/{connection_id}/quality-score
The account's own Quality Score fixer values (QSFIX, za-N11).
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 PATCH https://api.zinndigital.com/v1/ads/connections/{connection_id}/quality-score \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'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 action ads.qs_fix_settings. Each value is the customer's to set; null puts it back to the recommended value. 422 badQsFixSetting (naming the field) outside the bounds shown on GET, for a value that is not a whole number, or for an unknown field.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
enabled | boolean | No | — |
max_score | integer | No | — |
min_impressions | integer | No | — |
lcp_ms | integer | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsQsFixer | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429