POST /v1/ads/connections/{connection_id}/bid-ladder/{campaign_id}/switch

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}/bid-ladder/{campaign_id}/switch \
  -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.bid_ladder_switch. Only a row whose verdict is up or down (422 notPending otherwise, or while a switch is already waiting). The switch is proposed as a bids change and approved in one step (the click is the approval); the apply workflow sends it through the same gate as every write (kill switches, good standing) with its 30-day Undo. A new target starts at the campaign's own last-30-day cost per conversion or return. The 14-day learning freeze starts now.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429