> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asteroid.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> How the Asteroid API reports errors, and the problem types you can match on.

Error responses are JSON and follow [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) problem details.

```json theme={null}
{
  "type": "about:blank",
  "title": "Not Found",
  "status": 404,
  "detail": "Workflow not found",
  "instance": "/agents/v2/workflows/0b6e...",
  "code": 404,
  "message": "Workflow not found"
}
```

<ResponseField name="type" type="string">
  Identifies the problem. `about:blank` means the HTTP status says it all. Any other value is a URL on this site that documents the problem.
</ResponseField>

<ResponseField name="title" type="string">
  A short summary of the problem type.
</ResponseField>

<ResponseField name="status" type="integer">
  The HTTP status code.
</ResponseField>

<ResponseField name="detail" type="string">
  What went wrong with this request.
</ResponseField>

<ResponseField name="instance" type="string">
  The request path.
</ResponseField>

<ResponseField name="errors" type="object[]">
  The parameters that failed validation, on a `400`. Each item has `parameter` and `detail`.
</ResponseField>

`code` and `message` repeat `status` and `detail`, for older clients.

<Tip>
  Branch on `type` and `status`. Show `detail` to people. Do not parse `detail` or `message`: their text can change.
</Tip>

## Problem types

A problem type can add its own fields to the body. Its page lists them.

<CardGroup cols={2}>
  <Card title="Live limit reached" icon="gauge" href="/errors/limit-reached" horizontal>
    `429`: your organization is at a concurrency limit
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.