Delete Guardrail Policy
DELETE/api/advertising/guardrail-policies/:policy
Deletes a guardrail policy. Its scope falls back to the less specific policies from the next evaluation on. The tenant default policy cannot be deleted (422).
advertising:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Because deleting hands the policy's products and fields to broader policies, it passes the same gates as a write (403 without the advertising.approve permission when a gate applies, otherwise 422 on policy, mode or low_cover):
- the policy's products would fall under a broader policy in
autowithout a dry run of them (policy); - a narrower
autopolicy inherits fields from this one, and would inherit different values once it is gone (policy); - the effective low-cover band of a narrower policy would become incoherent (
low_cover).
Switch the affected auto policies to suggest, delete this policy, run a dry run, then switch them back to auto.
Requires the advertising.manage permission (and advertising.approve when one of the gates above applies). 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
Response Headers
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.