Run Guardrail Policy Dry Run
POST/api/advertising/guardrail-policies/:policy/dry-run
Queues a dry run of the policy: a background replay of the last 7 days that works out which changes the policy would have proposed, without sending anything to an ad platform. Returns immediately with tracked_job_log_id, the ID of the background job, which reports progress and a summary (changes proposed, products processed, estimated spend saved, accounts processed, signals). When it finishes, the results are stored on the policy as last_dry_run_at / last_dry_run_results; a dry run in the last 7 days is required before the policy can be switched to auto.
advertising:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
No request body.
Requires the advertising.manage permission. Personal access tokens need the advertising:write scope.
Request
Responses
- 200
- 401
- 403
- 404
- 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
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.