Get incident
Retrieve an incident with its status updates and affected monitors.
Get incident
GET /incidents/:id
Get incident with status updates and affected monitors.
Auth: Bearer token (read scope)
Request
bashcurl -H "Authorization: Bearer hu_..." \ "https://happyuptime.com/api/v1/incidents/inc_847"
Response
json{ "data": { "id": "inc_847", "project_id": "proj_xyz", "title": "API latency spike", "status": "investigating", "severity": "major", "started_at": "2026-03-07T14:22:00Z", "resolved_at": null, "created_at": "2026-03-07T14:22:00Z", "updated_at": "2026-03-07T14:35:00Z", "updates": [ { "id": "upd_001", "incident_id": "inc_847", "status": "investigating", "message": "We are investigating elevated API response times.", "is_internal": false, "created_at": "2026-03-07T14:22:00Z" }, { "id": "upd_002", "incident_id": "inc_847", "status": "identified", "message": "Root cause identified: database connection pool exhaustion.", "is_internal": false, "created_at": "2026-03-07T14:35:00Z" } ], "affected_monitors": [ { "id": "mon_abc123", "name": "API Server", "status": "degraded" } ] } }
Status lifecycle
Incidents move through four statuses:
| Status | Meaning |
|---|---|
investigating | Initial triage — cause unknown |
identified | Root cause found |
monitoring | Fix applied, watching for recovery |
resolved | Incident closed |