request_error
The request was refused as sent — a body that does not parse, a missing or malformed field, a /v1/execute validation failure, an unknown x-ace-skills pair, a Bedrock path/body modelId mismatch, an API key sent beside an access-key pair, a mode this deployment cannot serve.
What it means
The request was refused as sent — a body that does not parse, a missing or malformed field, a /v1/execute validation failure, an unknown x-ace-skills pair, a Bedrock path/body modelId mismatch, an API key sent beside an access-key pair, a mode this deployment cannot serve.
How to recognise it
The gateway answers HTTP 400 with x-ace-error: request_error on the response. This refusal has no typed envelope of its own, so the header is the reliable signal; the body is the surface's usual error shape.
Is it ACE or the provider?
x-ace-error is present only on errors ACE originated. A vendor error relayed from upstream — a real provider 429, a provider 401 for a bad pass-through key — carries no x-ace-error, and its own type and code mean what the provider says. Read the header before deciding whether to retry, re-mint a key or surface the error.
Other 400 errors
guardrail_violation: Prompt-injection or jailbreak guardrail tripped (names detected rule).
Related
- Error contracts & status codes: the full taxonomy
- Response header specification
- Echo mode: reproduce a call without spending