access_denied
HTTP status: 403
Retryable: No — retrying without changes will fail the same way.
The request was refused by a platform security control.
When it fires
A request was blocked by an account-level security control before it reached the endpoint. The response is intentionally generic — for the same anti-enumeration reason as `invalid_api_key`, we do not reveal which control fired or why, so a probing client learns nothing it can tune against.
How to handle it
This is not a per-request error to retry around — retrying produces the same response. If you believe the block is in error, contact support with your `request_id` (do not include applicant PII); support can investigate the specific control without exposing it on the wire.
Example response
{
"error": {
"type": "https://docs-dev.autohost-dev.uk/api/errors/access_denied",
"code": "access_denied",
"message": "Access denied",
"request_id": "req_01HEXAMPLE0000000000000000",
"doc_url": "https://docs-dev.autohost-dev.uk/api/errors/access_denied"
}
}