Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Edit the title, message, severity, status or affected monitors of an incident
status to resolved records the resolution time; moving a resolved incident to another status clears it. To post a message on the incident timeline, use Add Incident Update instead.
PATCH /api/projects/{projectId}/status-pages/{statusPageId}/incidents/{id}
| Header | Required | Description |
|---|---|---|
X-API-Key | Yes | Your API key (Authorization: Bearer {jwt} also works). API keys need the read_write scope. |
Content-Type | Yes | application/json |
X-Project-ID header is needed.
| Parameter | Type | Description |
|---|---|---|
projectId | UUID | The project |
statusPageId | UUID | The status page |
id | UUID | The incident |
| Field | Type | Description |
|---|---|---|
title | string | 1-200 characters |
message | string | 1-5000 characters |
severity | string | minor, major or critical |
status | string | investigating, identified, monitoring or resolved |
affected_monitor_ids | UUID[] | At least one monitor, each attached to this status page. Replaces the current list. |
{
"success": true,
"data": {
"incident": {
"id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b",
"status_page_id": "0b7c3a52-7d57-4c35-9f0e-5a3b6f1f2a10",
"incident_id": null,
"title": "Elevated API error rates",
"message": "The fix is rolling out.",
"severity": "major",
"status": "monitoring",
"affected_monitor_ids": ["a3f1c2d4-5b6e-4f70-8a91-b2c3d4e5f607"],
"published_at": "2026-09-30T12:00:00.000Z",
"updated_at": "2026-09-30T12:20:00.000Z",
"resolved_at": null,
"auto_published": false
}
}
}
| Status | Code | Cause |
|---|---|---|
| 400 | VALIDATION_ERROR | Invalid body, or a monitor in affected_monitor_ids is not attached to this status page |
| 401 | AUTHENTICATION_REQUIRED | Missing or invalid credentials, or the caller is not a project admin (message Access denied) |
| 403 | API_KEY_ORGANIZATION_MISMATCH | The API key belongs to a different organization than the project |
| 403 | READ_ONLY_API_KEY | The API key has the read scope |
| 404 | RESOURCE_NOT_FOUND | The status page or incident does not exist, or the incident belongs to a different status page |
curl -X PATCH https://api.uptimeio.com/api/projects/YOUR_PROJECT_ID/status-pages/YOUR_STATUS_PAGE_ID/incidents/YOUR_INCIDENT_ID \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "status": "monitoring", "message": "The fix is rolling out." }'
const base = 'https://api.uptimeio.com/api/projects/YOUR_PROJECT_ID/status-pages/YOUR_STATUS_PAGE_ID';
const response = await fetch(`${base}/incidents/YOUR_INCIDENT_ID`, {
method: 'PATCH',
headers: {
'X-API-Key': process.env.UPTIMEIO_API_KEY,
'Content-Type': 'application/json',
},
body: JSON.stringify({ status: 'monitoring' }),
});
const { data } = await response.json();
console.log(data.incident.status);
Was this page helpful?