Get Affected Monitors

List the monitors an incident affects

Overview

Returns the monitor the incident belongs to (check_id) followed by any monitors listed in affected_monitor_ids, ordered by name. Deleted monitors are omitted. Incidents with no monitors return an empty list.

GET /api/incidents/{id}/affected-checks

Authentication

X-API-Key: YOUR_API_KEY or Authorization: Bearer YOUR_JWT. A read-only key is sufficient.

Path parameters

Parameter	Type	Description
id	UUID	Incident ID.

Response

200 OK

{
  "success": true,
  "data": {
    "affected_checks": [
      {
        "id": "8d9e0f1a-2b3c-4d5e-8f6a-7b8c9d0e1f2a",
        "name": "Checkout API",
        "target": "https://shop.example.com/api/health",
        "type": "HTTP",
        "status": "active"
      }
    ]
  }
}

Field	Type	Description
id	UUID	Monitor ID.
name	string	Monitor name.
target	string	The monitored URL, host or target.
type	string	Monitor type: HTTP, TCP, ICMP, KEYWORD, DNS or HEARTBEAT.
status	string	The monitor’s configuration status: active, paused or disabled.

Errors

Status	Code	Cause
400	VALIDATION_ERROR	id is not a UUID.
401	MISSING_AUTH, INVALID_API_KEY, INVALID_TOKEN	Missing or invalid credentials.
404	RESOURCE_NOT_FOUND	No such incident in your project.

Example

cURL

curl https://api.uptimeio.com/api/incidents/3f6c1a52-9d1e-4b0a-8f7d-2a1b3c4d5e6f/affected-checks \
  -H "X-API-Key: YOUR_API_KEY"