Skip to main content

​
Overview

Retrieve a list of monitors/checks that are affected by or associated with a specific incident. For system incidents, this shows which probes detected failures. For manual incidents with multiple affected monitors, this shows all associated monitors.

​
Authentication

Requires API Key authentication:
  • API Key: X-API-Key: YOUR_API_KEY

​
Path Parameters

​
id
string
required
Incident ID (UUID). The unique identifier of the incident.

​
Response Format

​
success
boolean
Whether the request was successful
​
data
object

​
Example Requests

curl -X GET 'https://api.uptimeio.com/api/incidents/550e8400-e29b-41d4-a716-446655440000/affected-checks' \
  -H 'X-API-Key: YOUR_API_KEY'

​
Example Response

{
  "success": true,
  "data": {
    "affected_checks": [
      {
        "id": "660e8400-e29b-41d4-a716-446655440000",
        "name": "API Health Check",
        "target_url": "https://api.example.com/health",
        "type": "HTTP",
        "status": "down"
      },
      {
        "id": "770e8400-e29b-41d4-a716-446655440001",
        "name": "Database Connection",
        "target_url": "db.example.com:5432",
        "type": "TCP",
        "status": "down"
      },
      {
        "id": "880e8400-e29b-41d4-a716-446655440002",
        "name": "Payment Service",
        "target_url": "https://payments.example.com/status",
        "type": "HTTP",
        "status": "degraded"
      }
    ]
  }
}

​
Status Codes

StatusDescription
200 OKAffected checks successfully retrieved
401 UnauthorizedAuthentication failed or invalid credentials
404 Not FoundIncident not found or not accessible in current project
500 Internal Server ErrorServer error during retrieval

​
Error Codes

{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Incident not found"
  }
}

​
Understanding Affected Checks

​
For System Incidents

System incidents are triggered by probe executions on specific monitors. The affected checks list shows:
  • The primary monitor that triggered the incident (via check_id)
  • Other related monitors if multiple probes detected the same issue

​
For Manual Incidents

Manual incidents may be created with multiple affected monitors. The affected checks list shows:
  • All monitors specified in the affected_monitor_ids during incident creation
  • This helps track the blast radius of the outage

​
Monitor Status Values

The status field in the response indicates the monitor’s current state:
StatusMeaning
upMonitor is healthy and responding normally
downMonitor is failing all probes
degradedMonitor is responding but slower than expected or intermittently failing
unknownMonitor status cannot be determined (no recent checks)

​
Notes

  • The response shows monitors currently affected by the incident
  • Check statuses are real-time current statuses, not historical
  • Use the monitor ID to fetch additional monitor details from the monitors API
  • For system incidents, the primary check is the one that triggered the incident
  • An empty list means the incident has no associated monitors (rare, mostly for internal incidents)