GET /v1/ads/connections/{connection_id}/bid-ladder

Authentication

Send an API key as a bearer token. The key must carry the ads.view 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 GET https://api.zinndigital.com/v1/ads/connections/{connection_id}/bid-ladder \
  -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.view. One row per campaign, refreshed by the connection's daily audit (docs/1006 §39) — never a network call in the request. The ladder is clicks → Maximise conversions → target CPA (or target ROAS for a campaign that sends values), one step at a time; each step needs the network's published minimum conversions times our 1.5 margin (need in window_days; vendor_min and source say whose figure it is, verified when it was read). verdict: up / down (a one-click switch), not_yet, top, learning (switched in the last 14 days: no automatic budget raise, bid, keyword, negative or pause touches it until frozen_until), kept (a portfolio strategy, a goal the customer chose, or a type that picks its own bidding). review is the measured result 14 days after a switch. Steps first, kept last; at most 500.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 429