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

# Errors

Our API 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 indicate an error that resulted from the provided information (e.g. a required parameter was missing, validation errors, etc.), and codes in the `5xx` range indicate an actual error with our servers.

## HTTP Status Code Summary

| Status code                        | Description                                                                         |
| ---------------------------------- | ----------------------------------------------------------------------------------- |
| `200` OK                           | Everything worked as expected                                                       |
| `400` Bad Request                  | Often missing a required parameter or validation of a supplied parameter has failed |
| `401` Unauthorized                 | The oauth parameters provided to not have permission for this resource              |
| `402` Request Failed               | Parameters were valid but request failed                                            |
| `404` Not Found                    | The requested item does not exist                                                   |
| `500, 502, 503, 504` Server errors | Something went wrong on our end                                                     |

### Error/validation responses

Returned as status `400 Bad Request` on `POST` or `PUT` requests

```javascript
{"__all__": ["The provided error is related to the object as a whole"]}
```

```javascript
{"some_field": ["This field is required"]}
```

```javascript
{"nested_field": {"nested_field-1": {"some_field": ["This field is required"]}}}
```


---

# 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://api-docs.devhub.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.