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

# Status & Error Codes

> Every response includes a status object indicating success or the cause of an error.

## Status object

Every response includes the status object which indicates if the request was successful.
If it is not successful, `message` specifies the cause of the error.

```json theme={null}
{
  "status": {
    "code": 200,
    "message": "success"
  }
}
```

## Status and error codes

The CryptoQuant API uses standard HTTP status codes to indicate success or failure.
`200` represents success, `4xx` represents a user error (such as a problem with your key),
and `5xx` represents a problem with our API.

In the status object, the `code` field contains the status code and the `message` field
contains the type of response.

| Code  | Type                    | Description                                                                                                                       |
| ----- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `200` | `success`               | Request was successful.                                                                                                           |
| `200` | `deprecated`            | A resource is deprecated and will be removed in the future.                                                                       |
| `400` | `bad_request`           | Some required parameter is missing or has the wrong value.                                                                        |
| `401` | `unauthorized`          | Internal authorization failed. It might mean missing or wrong credentials.                                                        |
| `403` | `forbidden`             | You don't have access to the requested endpoint.                                                                                  |
| `404` | `not_found`             | URI is not valid or the resource ID does not correspond to an existing resource.                                                  |
| `405` | `not_allowed`           | HTTP method not allowed, such as attempting to use a POST request with an endpoint that only accepts GET requests, or vice versa. |
| `429` | `too_many_requests`     | The user has sent too many requests in a given amount of time.                                                                    |
| `500` | `internal_server_error` | Unexpected error occurred. Please report this when you see it.                                                                    |