> 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/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. Depending on auth failure mode, clients may see either `"Unauthorized"` or `"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 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://docs.intelligems.io/developer-resources/external-api/intelligems-external-api/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.