> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/introduction-to-arm-developer-apis/errors.md).

# Errors

AutoRABIT APIs follow standard HTTP response codes to signal the outcome of API requests. Understanding these codes helps in diagnosing issues and improving the stability of your integrations.

* **2xx** — Successful operations
* **4xx** — Client-side errors (e.g., invalid inputs, missing data)
* **5xx** — Server-side errors (typically rare)

## HTTP Status Code Summary <a href="#http-status-code-summary" id="http-status-code-summary"></a>

<table><thead><tr><th width="223">Error Code</th><th>Description</th></tr></thead><tbody><tr><td><strong>200 - OK</strong></td><td>The request succeeded as expected.</td></tr><tr><td><strong>400 - Bad Request</strong></td><td>The request was invalid—commonly due to missing or malformed parameters.</td></tr><tr><td><strong>401 - Unauthorized</strong></td><td>No valid API key was provided.</td></tr><tr><td><strong>402 - Request Failed</strong></td><td>The request was well-formed, but the operation failed.</td></tr><tr><td><strong>403 - Forbidden</strong></td><td>The API key lacks permissions to perform the action.</td></tr><tr><td><strong>404 - Not Found</strong></td><td>The requested resource could not be found.</td></tr><tr><td><strong>409 - Conflict</strong></td><td>The request conflicts with another operation (e.g., duplicate submission using the same token).</td></tr><tr><td><strong>429 - Too Many Requests</strong></td><td>The rate limit has been exceeded. Implement exponential backoff.</td></tr><tr><td><strong>500, 502, 503, 504 - Server Errors</strong></td><td>Internal AutoRABIT server issues. These errors are rare and usually temporary.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/introduction-to-arm-developer-apis/errors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.