Incident resources

GET /api/v1/incidents / MCP list_incidents: requires incidents:read.

Query	Accepted / default
days	Seven or 30; default 30
check_id	Optional owned check ID
state	Optional open or resolved
limit, cursor	Standard bounded pagination

Lists incidents overlapping the recent rolling window, including episodes that began earlier but remain open or resolved within it. This differs from daily history’s incident-start counts.

GET /api/v1/incidents/:id / get_incident: requires incidents:read and the incident ID. The ID must belong to a check in the bound account.

Both use this incident resource:

{
  "id": "123",
  "check_id": "check_EXAMPLE",
  "started_at": "2026-01-01T12:00:00Z",
  "resolved_at": null,
  "resolved": false,
  "duration_seconds": 120
}

Duration ends at recovery for resolved incidents and at the read time for ongoing incidents; it is a nonnegative number, not necessarily an integer. resolved_at is null for an open incident.

Cause, free-form notes/updates and notification details are deliberately omitted. There are no incident write or manual-resolution API operations. For operational context use the signed-in incident view.