> For the complete documentation index, see [llms.txt](https://docs.gomalomo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gomalomo.com/errors.md).

# Errors

Malomo uses conventional HTTP response codes to indicate success or failure of an API request. In general: Codes in the `2xx` range indicate success. Codes in the `4xx` range indicates that a request failed with the information provided. Codes in the `5xx` range indicate an error with Malomo's servers.

| HTTP STATUS CODE                   |                                           |
| ---------------------------------- | ----------------------------------------- |
| 200 - OK                           | Everything worked as expected             |
| 400 - Bad Request                  | The request couldn't be completed         |
| 401 - Unauthorized                 | No valid API key was provided             |
| 404 - Not Found                    | The requested resource could not be found |
| 500, 502, 503, 504 - Server Errors | We screwed up. Sorry!                     |

#### `400`, `401`, `404` and `5xx` Response Format

| ATTRIBUTE    |                                                                 |
| ------------ | --------------------------------------------------------------- |
| `code`       | The type of error returned                                      |
| `message`    | A human-readable message providing more details about the error |
| `request_id` | Unique identifier for a specific request                        |
| `status`     | HTTP status code                                                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.gomalomo.com/errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.