Overview
Update an existing incident on your status page. You can modify the title, message, severity, status, and affected monitors. Each update is tracked in the incident history.Authentication
All requests must include authentication via API Key:- API Key:
X-API-Key: YOUR_API_KEY
Request
Path Parameters
| Parameter | Type | Description |
|---|---|---|
projectId | UUID | The ID of the project |
statusPageId | UUID | The ID of the status page |
id | UUID | The ID of the incident |
Request Body
All fields are optional. Omit fields you don’t want to modify.| Field | Type | Description |
|---|---|---|
title | string | New incident title (1-200 characters) |
message | string | New incident message (1-5000 characters) |
severity | string | New severity: minor, major, critical |
status | string | New status: investigating, identified, monitoring, resolved |
affected_monitor_ids | UUID[] | New list of affected monitor IDs (min 1 if provided) |
Response
Returns the updated incident object.Response Fields
| Field | Type | Description |
|---|---|---|
id | UUID | Unique incident identifier |
status_page_id | UUID | Status page ID |
title | string | Updated incident title |
message | string | Updated incident message |
severity | string | Updated severity level |
status | string | Updated status |
affected_monitor_ids | UUID[] | Updated list of affected monitors |
created_at | timestamp | Creation timestamp (unchanged) |
updated_at | timestamp | Updated timestamp |
resolved_at | timestamp | null | Resolution timestamp |
Status Codes
| Status | Description |
|---|---|
200 | Incident updated successfully |
400 | Validation error (invalid data or monitors) |
401 | Unauthorized (missing or invalid token) |
403 | Forbidden (no permission to update incident) |
404 | Incident or status page not found |