# Incidents

### Incident object

| Field                | Type           | Description                                                |
| -------------------- | -------------- | ---------------------------------------------------------- |
| `id`                 | string         | Unique incident ID                                         |
| `title`              | string         | Incident title                                             |
| `description`        | string         | Latest description / initial description                   |
| `status`             | string         | `minor` or `major`                                         |
| `resolved`           | boolean        | Whether the incident is resolved                           |
| `created_at`         | string         | ISO 8601 timestamp                                         |
| `resolved_at`        | string \| null | ISO 8601 timestamp, or `null` if ongoing                   |
| `updated_at`         | string         | ISO 8601 timestamp of last update                          |
| `service`            | string         | Service name                                               |
| `service_urlname`    | string         | Service URL slug                                           |
| `service_status_url` | string         | URL of the service's own status page                       |
| `user_generated`     | boolean        | Whether this was a user-reported incident                  |
| `components`         | array          | Affected component names                                   |
| `updates`            | array          | Ordered list of incident updates (see below)               |
| `isdown_url`         | string \| null | Link to the incident on IsDown. `null` for custom services |

#### Update object

Each item in the `updates` array:

| Field         | Type   | Description                                                    |
| ------------- | ------ | -------------------------------------------------------------- |
| `status`      | string | One of `investigating`, `identified`, `monitoring`, `resolved` |
| `created_at`  | string | ISO 8601 timestamp                                             |
| `description` | string | Update message                                                 |

***

### Error responses

All errors follow the same format:

```json
{
  "errors": [
    {
      "status": 422,
      "title": "Unprocessable Entity",
      "detail": "Status must be 'minor' or 'major'"
    }
  ]
}
```


---

# Agent Instructions: 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:

```
GET https://dev.isdown.app/endpoints/incidents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.