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

# Errors

The API uses the following HTTP status codes:

* `200` - Success.
* `400` - Validation error (invalid query/body values). See Validation Error Shape below.
* `401` - Unauthorized (invalid or missing API key)
* `404` - Resource not found
* `429` - Rate limit exceeded
* `500` - Internal server error

#### Validation Error Shape

For invalid query/body values, the response returns HTTP `400` with this structure:

```json
{
  "errors": [],
  "properties": {
    "fieldName": {
      "errors": ["Validation message"]
    }
  }
}
```

The top-level `errors` array is reserved for request-level errors not attributable to a specific field and is empty for typical field-validation failures; per-field messages live under `properties.<fieldName>.errors`.

#### Unauthorized Error Messages

Unauthorized responses use an `error` string, and on this API the value is always `"Unauthorized"` — for a missing header, an empty header, or any invalid key:

```json
{ "error": "Unauthorized" }
```


---

# 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://docs.intelligems.io/developer-resources/external-api-dev/intelligems-external-api/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.