ads

POST /v1/ads/connections/{connection_id}/objectives/{campaign_id}/approve

A person's approval puts the proposed objective in force (za-184).

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}/objectives/{campaign_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 action ads.objective_approve. 422 badState when nothing is proposed. The account's audit starts at once: the bid-strategy ladder then judges the campaign against the objective. Any switch it implies is the ladder's own proposal — one step at a time, on the networks' minimums plus our margin, never while the campaign learns (the 14-day freeze), and sent only through the change queue with its Undo.

Parameters

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

Response

NameTypeRequiredWhat it is
dataAdsCampaignObjectiveRowYesOne campaign's objective, its proposal and the judgement against it (za-184).

Errors this endpoint can return

401 · 403 · 404 · 422 · 429