> For the complete documentation index, see [llms.txt](https://dev.isdown.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.isdown.app/endpoints/incidents/create-an-incident.md).

# Create an incident

<mark style="color:blue;">`POST`</mark> `https://isdown.app/api/v2/incidents`

### Request body

| Parameter          | Type    | Required | Description                                                                             |
| ------------------ | ------- | -------- | --------------------------------------------------------------------------------------- |
| `service_id`       | integer | Yes      | The numeric ID of the custom service                                                    |
| `title`            | string  | Yes      | Short title describing the incident                                                     |
| `status`           | string  | No       | `minor` or `major`. Defaults to `minor`                                                 |
| `description`      | string  | No       | Initial update message. Defaults to empty string                                        |
| `resolution_stage` | string  | No       | `investigating`, `identified`, `monitoring`, or `resolved`. Defaults to `investigating` |

### Example request

```bash
curl -X POST https://api.isdown.app/api/v2/incidents \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "service_id": 1234,
    "title": "API response times elevated",
    "status": "minor",
    "description": "We are seeing elevated response times on our API.",
    "resolution_stage": "investigating"
  }'
```

### Example Response

```bash
{
  "data": {
    "id": "55001",
    "type": "incidents",
    "attributes": {
      "url": null,
      "title": "API response times elevated",
      "description": "We are seeing elevated response times on our API.",
      "status": "minor",
      "resolved": false,
      "created_at": "2024-03-15T10:00:00.000Z",
      "resolved_at": null,
      "updated_at": "2024-03-15T10:00:00.000Z",
      "service_id": 1234,
      "service": "My API",
      "service_status_url": null,
      "service_urlname": "my-api",
      "user_generated": false,
      "severity_from_provider": null,
      "components": [],
      "updates": [
        {
          "status": "investigating",
          "created_at": "2024-03-15T10:00:00.000Z",
          "description": "We are seeing elevated response times on our API."
        }
      ],
      "isdown_url": null
    }
  }
}
```

#### Notes

* Creating an incident automatically updates the service status on any linked status pages
* Subscribers to your status page will be notified according to your notification settings
* Setting resolution\_stage to resolved immediately marks the incident as resolved


---

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

```
GET https://dev.isdown.app/endpoints/incidents/create-an-incident.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.