All errors follow a consistent JSON format with a machine-readableDocumentation Index
Fetch the complete documentation index at: https://api-docs.hrizn.io/llms.txt
Use this file to discover all available pages before exploring further.
code and human-readable message.
Error response format
| Field | Description |
|---|---|
code | Machine-readable error code (see table below) |
message | Human-readable explanation |
details | Additional context (optional) |
request_id | Unique request identifier for support (optional) |
Always include the
request_id when contacting support about a failed request. It allows the team to trace the exact request through the system.Error Handling Decision Tree
Use this diagram to determine the correct recovery strategy for each error class:HTTP status codes
| Status | Meaning |
|---|---|
200 | Request succeeded |
201 | Resource created |
202 | Async operation accepted and started |
204 | Deleted (no response body) |
400 | Invalid request parameters |
401 | Authentication failed |
403 | Authenticated but lacking permissions |
404 | Resource not found or not accessible |
409 | Idempotency conflict |
429 | Rate limit exceeded |
500 | Server error |
Error codes
| Code | Status | Description |
|---|---|---|
validation_error | 400 | Request body or parameters failed validation |
unauthorized | 401 | Missing or invalid API key |
key_expired | 401 | API key has expired |
key_revoked | 401 | API key has been revoked |
forbidden | 403 | Key lacks the required scope |
not_found | 404 | Resource does not exist or is not accessible to this key |
idempotency_conflict | 409 | Same idempotency key used with different parameters |
rate_limit_exceeded | 429 | Too many requests |
internal_error | 500 | Unexpected server error |
