Reject Change Set
POST/api/advertising/change-sets/:changeSet/reject
Rejects a change set that is pending approval. Nothing is sent to the ad platform; every pending line is marked skipped with the reason, and any open approval request for the set is cancelled.
advertising:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body fields:
reason(required, string, max 2000): why the set was rejected; returned asrejected_reason.
Returns 422 when the set is no longer pending approval or has expired.
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.