API reference
Errors
Errors use the vendor's own JSON shape: OpenAI-style on OpenAI endpoints, Anthropic-style on /v1/messages. Every message ends with the request ID.
| Status | Code | Meaning |
|---|---|---|
| 400 | bad_request | The request body is malformed. |
| 401 | missing_api_key · invalid_api_key · expired_api_key | No key, a revoked key or an expired key. |
| 402 | billing_required · tenant_suspended | The organisation can't send traffic yet. |
| 403 | policy_denied (or the rule's code) | Policy blocked the request. The reason names the rule. |
| 403 | held_for_review | Waiting for a human reviewer under Reviews. |
| 403 | attachments_blocked · guard_model_blocked | Files aren't allowed, or a guard model refused the content. |
| 429 | budget_exceeded · plan_limit_reached | A workload budget or the plan's monthly requests were used up. |
| 501 | not_governed | The endpoint can't be inspected, so it isn't served. |
| 502 | upstream_unavailable · served_model_mismatch | No allowed provider answered, or one served a model policy didn't allow. |
Policy refusals in detail
| Code | Why |
|---|---|
data_blocked | The request contained data the profile blocks, such as card numbers or secrets. |
prompt_injection | The message looked like an attempt to override instructions. |
denied_topic | The message mentions a topic the profile blocks. |
prompt_too_large | The message is bigger than the profile allows. |
output_guard_blocked | The safety model judged the answer unsafe, so it was withheld. |
Example
{
"error": {
"message": "Card details are not allowed by this profile (request 7f3c…)",
"type": "governance_error",
"code": "data_blocked"
}
}Look the request ID up in Requests to see the full decision trace. See Why was a request blocked? for what to do about each one.