> For the complete documentation index, see [llms.txt](https://apis.rightrev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apis.rightrev.com/getting-started/http-status-codes.md).

# HTTP Status Codes

The below are the HTTP status codes for every API request. The status codes indicate whether a particular HTTP request has been successfully completed

|     |                       |                                                                                                   |
| --- | --------------------- | ------------------------------------------------------------------------------------------------- |
| 200 | OK                    | The request has succeeded                                                                         |
| 201 | Created               | The request has been fulfilled and resulted in a new resource being created                       |
| 204 | No Content            | The server successfully processed the request, but there is no content to return for this request |
| 400 | Bad Request           | The request could not be understood by the server due to invalid syntax                           |
| 401 | Unauthorized          | The request requires user authentication                                                          |
| 403 | Forbidden             | User does not have permission to access the API                                                   |
| 404 | Not Found             | The server could not find the requested resource                                                  |
| 409 | Conflict              | The request could not be completed due to a conflict with the current state of the resource       |
| 412 | Precondition Failed   | The server does not meet one of the preconditions that the requester put on the request           |
| 500 | Internal Server Error | The server encountered an unexpected condition which prevented it from fulfilling the request     |


---

# 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://apis.rightrev.com/getting-started/http-status-codes.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.