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

# Errors

<Note>
  This page covers the general shape of error responses. The full catalog of specific error codes and messages is still being finalized and will be added here as it's confirmed.
</Note>

## Response envelope

Relaybase API responses share a consistent envelope. A successful response looks like this:

```json theme={null}
{
  "data": { ... },
  "message": "result",
  "status": 200,
  "success": true
}
```

An error response follows the same shape, with `success` set to `false` and `status` set to the relevant HTTP status code.

## HTTP status codes

`200` confirms a successful request — you'll see this in the `status` field of every example on this site.

Beyond that, the standard conventions you'd expect from a REST API generally apply (`401` for auth problems, `422` for a malformed request body, `429` for rate limiting, `500` for a server-side failure), but Relaybase hasn't published a confirmed, endpoint-by-endpoint mapping of status codes and error responses yet.

<Note>
  Exact error messages, machine-readable error codes, and per-endpoint status code behavior will be documented here once finalized — treat the codes above as general guidance, not a confirmed contract, until then.
</Note>