# Errors

Our API returns standard HTTP success or error status codes. For errors, we will also include extra information about what went wrong encoded in the response as JSON. The various HTTP status codes we might return are listed below. 

{% hint style="info" %}
When requesting data to graphQL endpoints you will always get a 200 OK response, In those cases look for object \`errors\` to find the error information.
{% endhint %}

### HTTP StatusCode <a href="#errors-http-status-codes" id="errors-http-status-codes"></a>

| Code | Title                 | Description                     |
| ---- | --------------------- | ------------------------------- |
| 200  | OK                    | The request was successful.     |
| 400  | Bad request           | Bad request                     |
| 403  | Unauthorized          | Your API key is invalid.        |
| 404  | Not found             | The resource does not exist.    |
| 429  | Too Many Requests     | The rate limit was exceeded.    |
| 50X  | Internal Server Error | An error occurred with our API. |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://api-docs.everreal.co/helpers/errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.