ads

POST /v1/ads/connections/{connection_id}/budget-decisions/{key}/settle

Answer or end one of the customer's budget decisions (za-84).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

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}/budget-decisions/{key}/settle \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "answer": <string<keep, revert>> }'

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.own_budget_settle. answer keep — the amount stays; revert — back to the amount before the decision (proposed and approved together, sent by the apply workflow; change is it). Either way the decision ends, its question closes, and the autopilot may look after the budget again. Refusals (422): ownBudgetBadAnswer, ownBudgetNotOpen.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—
key (path)stringYes—

Request body

NameTypeRequiredWhat it is
answerstring<keep, revert>Yes—

Response

NameTypeRequiredWhat it is
dataAdsBudgetDecisionYesThe customer's own budget for one campaign (za-84, docs/1006 §84).
changeAdsChange | nullYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429