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

# Errors

> How Blockradar communicates errors and how to handle them.

The Blockradar API uses standard HTTP status codes to indicate whether a request succeeded or failed. When a request fails, the response body contains a `message` field describing what went wrong.

## HTTP status codes

| Code  | Meaning                                                                  |
| ----- | ------------------------------------------------------------------------ |
| `200` | Success. The request completed as expected.                              |
| `400` | Bad request. A required parameter is missing or malformed.               |
| `401` | Unauthorized. Your API key is missing or invalid.                        |
| `403` | Forbidden. Your API key does not have permission for this action.        |
| `404` | Not found. The requested resource does not exist.                        |
| `422` | Unprocessable entity. The request was well-formed but failed validation. |
| `429` | Too many requests. You have exceeded the rate limit.                     |
| `500` | Internal server error. Something went wrong on our end.                  |

## Error response format

```json theme={null}
{
  "statusCode": 400,
  "message": "walletId is required"
}
```

## Handling errors

Check the `statusCode` field on every response. For `4xx` errors, inspect `message` to understand what to fix. For `500` errors, retry with exponential backoff and contact support if the issue persists.

<Card title="Full API Reference" icon="book" href="/en/api-reference/errors">
  View the errors reference in the API Reference tab.
</Card>