# Edit an incident

`PATCH https://evohub.io/api/v1/pages/{pageID}/incidents/{id}`

Part of the [Status API](https://docs-dev.evohub.io/status.md) reference · operationId `updateIncident`.

Edits the title, impact or status; a field left out keeps its value. This adds
no timeline entry and mails nobody: post an update for that.

**Permission (API-key scope):** `status:incident:write`.

## Authorization

Any one of:

- `bearerAuth` (status:incident:write)
- `apiKeyHeader` (status:incident:write)

Where:

- `bearerAuth`: HTTP Bearer — An EvoHub API key (`evohub_…`) as a bearer token.
- `apiKeyHeader`: API key in the header `X-API-Key` — An EvoHub API key (`evohub_…`).

## Path parameters

- `pageID` (string (uuid), required, example `3f6c2a1e-8b4d-4f7a-9c21-5d0e7a9b1c42`): The status page's id (a UUID).
- `id` (string (uuid), required): The incident's, maintenance window's or subscriber's id (a UUID).

## Request body (required)

Content type: `application/json`

Type: `IncidentPatch`

A field left out keeps its value.

- `title` (string)
- `impact` (IncidentImpact, one of `none`, `minor`, `major`, `critical`)
- `status` (IncidentStatus, one of `investigating`, `identified`, `monitoring`, `resolved`)

## Responses

### 200 — The incident.

Content type: `application/json`

Type: `object`

- `data` (Incident, required)
  - `id` (string (uuid), required)
  - `org_id` (string, required)
  - `page_id` (string (uuid), required)
  - `title` (string, required)
  - `impact` (IncidentImpact, required, one of `none`, `minor`, `major`, `critical`)
  - `status` (IncidentStatus, required, one of `investigating`, `identified`, `monitoring`, `resolved`)
  - `started_at` (string (date-time), required)
  - `resolved_at` (string (date-time))
  - `created_at` (string (date-time), required): When the page got it.
  - `updated_at` (string (date-time), required)
  - `postmortem_body` (string): Markdown; absent when none is written.
  - `postmortem_published_at` (string (date-time)): Set while the postmortem shows on the public page.
  - `backfilled` (boolean, required): Written after the fact with its own past times; it mailed no subscriber.
  - `managed_in` (ManagedIn, required, one of `oncall`, `status_page`)
  - `affected_component_ids` (array of string (uuid), required)
  - `updates` (array of IncidentUpdate, required): The timeline.
    - `id` (string (uuid))
    - `incident_id` (string (uuid))
    - `status` (IncidentStatus, one of `investigating`, `identified`, `monitoring`, `resolved`)
    - `body` (string)
    - `created_at` (string (date-time))
- `success` (boolean, required, value `true`)

### 400 — A field is missing or invalid (`VALIDATION_ERROR`); the message names it, or the body is not valid (`INVALID_BODY`).

Content type: `application/json`

Type: `Error`

- `error` (object, required)
  - `code` (string, required): Machine-readable code. Branch on this.
  - `message` (string, required): Human-readable explanation.
  - `request_id` (string): This request's id, also in `X-Request-ID`.

### 401 — No API key was sent, or it is unknown, revoked or expired (`UNAUTHORIZED`).

Content type: `application/json`

Type: `Error`

- `error` (object, required)
  - `code` (string, required): Machine-readable code. Branch on this.
  - `message` (string, required): Human-readable explanation.
  - `request_id` (string): This request's id, also in `X-Request-ID`.

### 403 — The key lacks the scope this endpoint needs (`FORBIDDEN`).

Content type: `application/json`

Type: `Error`

- `error` (object, required)
  - `code` (string, required): Machine-readable code. Branch on this.
  - `message` (string, required): Human-readable explanation.
  - `request_id` (string): This request's id, also in `X-Request-ID`.

### 404 — No such page or incident, or one on another page (`NOT_FOUND`).

Content type: `application/json`

Type: `Error`

- `error` (object, required)
  - `code` (string, required): Machine-readable code. Branch on this.
  - `message` (string, required): Human-readable explanation.
  - `request_id` (string): This request's id, also in `X-Request-ID`.

### 429 — Too many requests (`RATE_LIMITED`). Wait `Retry-After` seconds.

Headers:

- `Retry-After` (integer): Seconds to wait.

Content type: `application/json`

Type: `Error`

- `error` (object, required)
  - `code` (string, required): Machine-readable code. Branch on this.
  - `message` (string, required): Human-readable explanation.
  - `request_id` (string): This request's id, also in `X-Request-ID`.

### 500 — Something went wrong on EvoHub's side (`INTERNAL_ERROR`). Retry later.

Content type: `application/json`

Type: `Error`

- `error` (object, required)
  - `code` (string, required): Machine-readable code. Branch on this.
  - `message` (string, required): Human-readable explanation.
  - `request_id` (string): This request's id, also in `X-Request-ID`.

## Example request

```bash
curl -X PATCH 'https://evohub.io/api/v1/pages/3f6c2a1e-8b4d-4f7a-9c21-5d0e7a9b1c42/incidents/00000000-0000-0000-0000-000000000000' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <TOKEN>' \
  -d '{
  "impact": "minor"
}'
```