Regenerate Guardrail Signal Change Set
POST/api/advertising/signals/:signal/regenerate
Replaces a signal's pending change set that was planned under an older guardrail policy. The pending set is rejected (reason "Regenerated under the current guardrail policy."), the signal is unlinked from it, and a guardrail evaluation of the signal's ad account is queued so a new set is proposed under the current policy. Responds 202 Accepted; the new set appears on the signal after the evaluation runs.
advertising:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
No request body. Returns 422 when the signal has no change set pending approval, or the pending set already follows the current policy.
Requires the advertising.manage permission. Personal access tokens need the advertising:write scope.
Request
Responses
- 202
- 401
- 403
- 404
- 422
- 429
Accepted
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
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.