Approve Change Set
POST/api/advertising/change-sets/:changeSet/approve
Approves a change set that is pending approval and queues it to be applied to the ad platform. The apply runs in the background: the response has status approved and a top-level tracked_job_log_id for the apply job (null when the set still needs further approvers). Poll Get Change Set for the outcome; after applying, each line is read back from the platform to verify it, and lines whose live value changed outside SKU.io since the set was made are skipped (skipped_drift) rather than overwritten.
advertising:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Send line_ids to approve only some lines; the other pending lines are marked skipped. Omit it (or send null) to approve every pending line. When you approve a selection, the caps, the estimated spend delta and the approval tier are re-evaluated for the selected lines only, so caps_breached (and the need for confirm_caps_breached) reflects what will actually apply: a selection can clear a breach the whole set had, or still break a cap.
When the tenant uses a tiered approval policy for ad change sets, this records your approval on the approval request; the set applies only once the request is fully approved.
Body fields:
line_ids(optional, array of distinct integers, at least 1 when present): the IDs of pending lines to approve.confirm_caps_breached(optional, boolean): must betruewhen the set'scaps_breachedis not empty. A set outside the automation caps (blast radius, bid or budget change size, set size) never applies without this explicit confirmation. A breach of the approval-policy spend threshold is covered by the approval request instead and does not need it.
Returns 422 when the set breaks a cap and confirm_caps_breached is not true (error key caps_breached), when the set is no longer pending (already decided, or expired after its approval window), when the kill switch is on for the account, when a listed line is not a pending line of this set, or when you may not approve under the approval policy.
Returns 409 (error key superseded) when the set was replaced by an edited copy (see Revise Change Set); the message names the replacement to decide on instead.
Requires the advertising.approve permission. Personal access tokens need the advertising:write scope.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not Found
Response Headers
Conflict
Response Headers
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.