> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rangler.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors fields

> Definitions, types, allowed values, and defaults for errors.

Use this reference with the endpoint documentation. A required field must be present; a nullable field can still contain `null`. Missing data does not mean zero. See [Field guide](/field-guide) for unit and status conventions.

<a id="error-envelope" />

## Error envelope

| Field | Type | Presence | Meaning |
| - | - | - | - |
| `error` | [Error object](/fields/errors#error-object) | required | Error details returned when the request fails. |

<a id="error-object" />

## Error object

| Field | Type | Presence | Meaning |
| - | - | - | - |
| `type` | string | required | Error category, such as unauthorized or validation\_error. |
| `code` | string | required | Machine-readable error code for programmatic handling. |
| `message` | string | required | Human-readable explanation of why the request failed. |
| `request_id` | string | required | Request identifier to include when contacting support. |
| `details` | object or array of object or null | optional | Additional structured error details when available; its shape depends on the error. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.