POST /v1/ads/connections/{connection_id}/findings/{finding_id}/{action}

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}/findings/{finding_id}/{action} \
  -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 action ads.finding_apply / ads.finding_dismiss. apply on a suggestion (suggested: true) approves it and starts the account's audit, which makes exactly that change through the account's own guards (kill switches, good standing, the spend ceilings, the tracking hold) with its Undo; on a budget-limited campaign with a campaign that can give (can_apply), it proposes the move — the giving campaign's budget down and this one's up by the same amount, in ONE request — and approves it in one step (the apply workflow sends it; 30-day Undo). dismiss closes it; a dismissed finding stays dismissed. 422 notPending when it is no longer open, 422 badAction when there is nothing to apply.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429