List Incidents (Organization)
Lists incidents for an organization. If organizationId is omitted, the API falls back to the organization from your session.
GET /api/incidents
Readonly users only see incidents for customers they are assigned to.
Authentication
Requires a valid session.
- Header:
Authorization: Bearer <token>
Query Parameters
organizationId(optional): Organization ID. Defaults to your session organization.source(optional): Filter by incident source.manualreturns status-page announcements created by an admin;monitorreturns incidents generated automatically by the monitoring workers. Any other value is ignored and all sources are returned. Useful because manual incidents can be far older than the newest monitor incidents and would otherwise fall outside thelimitwindow.limit(optional, default:100, max:500): Maximum number of incidents to return.offset(optional, default:0): Pagination offset.includeTotal(optional, default:0): If set to1(ortrue), the response includestotal,limit, andoffset.onStatusPage(optional):trueor1returns only incidents a status page shows as an incident: manual ones and those linked to a status page. Other values thantrue,false,1,0answer400.
Example (cURL)
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"
curl -X GET "$BASE_URL/api/incidents?organizationId=1" \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/json"To paginate:
curl -X GET "$BASE_URL/api/incidents?organizationId=1&limit=100&offset=0" \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/json"To list only manually created (status-page) incidents:
curl -X GET "$BASE_URL/api/incidents?organizationId=1&source=manual" \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/json"Example Response (excerpt)
[
{
"id": 123,
"websiteId": 101,
"status": "open",
"severity": "downtime",
"startedAt": "2026-02-26T12:10:00.000Z",
"resolvedAt": null,
"lastNotifiedAt": "2026-02-26T12:11:00.000Z",
"errorMessage": "Timeout",
"statusCode": null,
"responseTimeMs": null,
"website": {
"id": 101,
"name": "Main Marketing Site",
"url": "https://deinkunde.com",
"status": "active"
},
"customer": {
"id": 12,
"email": "ops@deinkunde.com",
"company": "Acme Corp"
}
}
]If includeTotal=1, the response shape changes to:
{
"incidents": [],
"total": 1234,
"limit": 100,
"offset": 0
}statusPages (since 28 October 2026): every entry carries [{ "id", "publicId", "name" }], the status pages the incident is shown on as an incident: linked pages, and for a manual incident with a customer the pages of that customer. Empty for a monitor incident that is not linked.
publicTitle, publicStatus, publicResolvedAt (since 28 October 2026): the incident as status pages show it. publicTitle is the title set for the pages or null (the pages then show title). publicStatus is open or resolved; for a monitor incident timeline updates set it independently of status, otherwise it follows status. publicResolvedAt is when it was resolved on the pages.
Deprecated fields: started_at, resolved_at, last_notified_at, error_message, status_code and response_time_ms are still sent next to startedAt, resolvedAt, lastNotifiedAt, errorMessage, statusCode and responseTimeMs until they are removed on 2027-01-18, with and without includeTotal. Read the camelCase fields.
Manual incidents without a customer
Since 27 October 2026 a manual incident can be created without a customer, linked to status pages only. The list includes it for organization-wide roles and tokens with customer: null; a customer-scoped login or token does not see it.
Common Errors
400 Organization ID is requiredif the API cannot infer an organization401 Unauthorizedif you are not authenticated403 Forbiddenif you do not have access to the organization500 Failed to fetch incidentson unexpected errors