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

# HTTP Status Codes

NVIDIA Run:ai APIs use standard HTTP status codes to indicate whether a request succeeded or failed.

## Success Responses

| Status code        | Meaning                                                 |
| ------------------ | ------------------------------------------------------- |
| **200 OK**         | The request succeeded.                                  |
| **202 Accepted**   | The request was accepted but is still being processed.  |
| **204 No Content** | The request succeeded and no response body is returned. |

## Client Error Responses (4xx)

| Status code                | Meaning                                                |
| -------------------------- | ------------------------------------------------------ |
| **400 Bad Request**        | The request is invalid.                                |
| **401 Unauthorized**       | Authentication failed.                                 |
| **403 Forbidden**          | The caller is authenticated but not authorized.        |
| **404 Not Found**          | The requested resource does not exist.                 |
| **405 Method Not Allowed** | The method is not allowed for this endpoint.           |
| **409 Conflict**           | The request conflicts with the current resource state. |

## Server Error Responses (5xx)

| Status code                   | Meaning                                                                              |
| ----------------------------- | ------------------------------------------------------------------------------------ |
| **500 Internal Server Error** | An unexpected server error occurred.                                                 |
| **501 Not Implemented**       | The server does not support the requested functionality.                             |
| **502 Bad Gateway**           | The gateway received an invalid response from an upstream service.                   |
| **503 Service Unavailable**   | The service is temporarily unavailable or an internal service dependency is failing. |
| **504 Gateway Timeout**       | The gateway timed out waiting for an upstream service.                               |


---

# 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://run-ai-docs.nvidia.com/api/2.21/getting-started/using-the-rest-api/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.