Writes and guardrails
How changes to an Amazon account work on Build: caps, a dry run, idempotency keys, a 24 hour undo and an audit log.
On this page
What you can change
Bids, budgets, negatives and campaigns on Amazon Ads. Changes stay off until you turn them on, and a key needs the read and write scope.
Change a target on an Amazon Ads account, behind caps, a dry run and undo.
Caps
Nothing moves past your limit. A request above a cap returns 422 and nothing is applied.
To write: where caps are set (console or API), which caps exist (bid, budget), and the default values
Dry run
A dry run shows what would change before anything is applied.
To write: how to ask for a dry run (parameter name), and a real dry-run response
Idempotency keys
To write: the idempotency header or field, how long a key is remembered, and what a repeated request returns
What a refused change looks like
A bad bid gets a 422, not a live campaign:
{ "status": 422, "message": "bid 2.40 is above this account's ceiling of 2.00." }
Your code lowers the bid and tries again. The call that succeeds returns 200, is logged, and can be undone for 24 hours.
Undo for 24 hours
To write: how to undo a change: the endpoint or console action, and what cannot be undone
Audit log
Every write is logged: who, what, and the result.
To write: where to read the audit log (console and API) and the fields in an entry
Approval mode
To write: what approval mode is, where it is turned on, and how a proposed change waits for a person to approve it
Last updated 30 Oct 2026