ads
POST /v1/ads/connections/{connection_id}/page-fixes/{fix_id}/approve
Apply the fix to the page on the site (za-210).
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 POST https://api.zinndigital.com/v1/ads/connections/{connection_id}/page-fixes/{fix_id}/approve \
-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.manage, audit-logged. Writes the edited page through a compare-and-swap on the box: only over the exact bytes snapshotted when the fix was written (a page changed since fails with pageFixChangedSince and keeps the customer's edit). Twice is once. 422 pageFixState, pageFixNotInGoodStanding.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
fix_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AdsPageFix | Yes | za-210 (docs/1006 §111): a landing-page fix applied on a page hosted with us — the text edits, the page file, its state, and the before/after measurement (landing-page Quality… |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429