ads

POST /v1/ads/changes/{change_id}/{action}

Approve, reject or undo one change.

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/changes/{change_id}/{action} \
  -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.change_<action>. approve sends exactly the proposed request to Google in the background (202); a kill switch, the spend ceiling or the organisation's standing can still refuse it (refused). undo sends the change's inverse (202) — allowed with the kill switch on. reject answers 200.

Parameters

NameTypeRequiredWhat it is
change_id (path)stringYes—
action (path)string<approve, reject, undo>Yes—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYes—
connection_idstringYes—
action_classstringYes—
statusAdsChangeStatusYes—
summaryobjectYes—
budget_delta_minorobjectYes—
proposed_bystringYes—
proposed_atstringYes—
decided_bystringYes—
decided_atobjectYes—
applied_atobjectYes—
undoablebooleanYes—
undo_untilobjectYes—
undone_atobjectYes—
errorstringYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429