Enforcer v3 docs / Enforcer Error Reference
10Errors
10
Reference
Errors
Every failure returns the same shape, so you can branch on error and show message.
{ "success": false, "error": "tenant_not_found", "message": "no tenant matches this credential" }
These are the slugs observed in production. It is not yet the complete set; anything not listed still follows the shape above.
| Slug | Status | What it means | What to do |
|---|---|---|---|
missing_token | 401 | No credential on a call that needs one. | Send Authorization: Bearer or X-API-Key. |
missing_credential | 401 | The same, on the MCP endpoint. | Send X-API-Key, or complete the OAuth flow. |
unauthenticated | 401 | The credential was rejected or has been revoked. | Get a fresh one. Do not retry the same value. |
missing_fields | 400 | A required field is absent. | Read the message; it names the fields. |
tenant_not_found | 404 | No tenant matches the code or credential you sent. | Check the tenant code. A wrong code and a deleted tenant look the same. |
cross_tenant_member | 403 | You tried to act on someone in another tenant. | Not a permission you can be granted; the engine refuses it. |
bad_request | 400 | The body did not parse, or a value is out of range. | Check types against the OpenAPI spec. |