ads

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

Say no to the step a ladder row proposes (za-183).

All ads endpoints

All developer docs →

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}/dismiss \
  -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_dismiss. The row is asked again only for a DIFFERENT step. 422 notPending when the row proposes nothing.

Parameters

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

Response

NameTypeRequiredWhat it is
dataAdsBidLadderRowYesOne campaign on the bid-strategy ladder (za-183, docs/1006 §39).

Errors this endpoint can return

401 · 403 · 404 · 422 · 429