Get Status Page Incident Updates

List the timeline updates of an incident

Overview

Returns every update posted to an incident, oldest first. The list is not paginated.

GET /api/projects/{projectId}/status-pages/{statusPageId}/incidents/{id}/updates

Authentication

Header	Required	Description
X-API-Key	Yes	Your API key (Authorization: Bearer {jwt} also works). Read-only keys are fine.

Required access: project viewer or higher. No X-Project-ID header is needed.

Path parameters

Parameter	Type	Description
projectId	UUID	The project
statusPageId	UUID	The status page
id	UUID	The incident

Response

200 OK

{
  "success": true,
  "data": {
    "updates": [
      {
        "id": "f0e1d2c3-b4a5-4968-8796-a5b4c3d2e1f0",
        "status_page_incident_id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b",
        "message": "We have identified the cause and are deploying a fix.",
        "status": "identified",
        "posted_at": "2026-09-30T12:10:00.000Z"
      },
      {
        "id": "0a1b2c3d-4e5f-4a6b-8c7d-9e0f1a2b3c4d",
        "status_page_incident_id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b",
        "message": "This incident has been resolved.",
        "status": "resolved",
        "posted_at": "2026-09-30T12:40:00.000Z"
      }
    ],
    "total_count": 2
  }
}

Update fields are described on Add Incident Update.

Errors

Status	Code	Cause
401	AUTHENTICATION_REQUIRED	Missing or invalid credentials, or no access to the project (message Access denied)
403	API_KEY_ORGANIZATION_MISMATCH	The API key belongs to a different organization than the project
404	RESOURCE_NOT_FOUND	The status page or incident does not exist, or the incident belongs to a different status page

Example

cURL

curl https://api.uptimeio.com/api/projects/YOUR_PROJECT_ID/status-pages/YOUR_STATUS_PAGE_ID/incidents/YOUR_INCIDENT_ID/updates \
  -H "X-API-Key: YOUR_API_KEY"