Uptime API › Monitors
List monitors that need attention
The caller's active monitors that are down or degraded: down ones
first, then by how long they have been in that state, oldest first.
since is when the monitor went down (from its open outage) or when
its slow alert was raised.
incident_id and cause are filled for a down monitor with an open
outage, and only when the caller also holds uptime:incident:read;
otherwise they are null.
Requires the uptime:monitor:read scope.
Authorization
Parameters
Query parameters
team_idstringNarrow to one team's monitors, ornonefor only the organization-wide ones. It never widens what the caller can see.limitintegerHow many monitors to return. Values above 100 are read as 100.
Responses
200
The monitors needing attention; an empty list when all is well.
dataarray of AttentionMonitorShow AttentionMonitor properties
idstring requirednamestring requiredlast_statusstring requiredsincestring (date-time) | null requiredincident_idstring | null requiredcausestring | null required
400
limit is not a positive integer (INVALID_LIMIT).
errorobject requiredcodestring requiredmessagestring requiredrequest_idstring
401
No API key was sent, or it is unknown, revoked or expired (UNAUTHORIZED).
errorobject requiredcodestring requiredmessagestring requiredrequest_idstring
403
The key lacks the scope this endpoint needs (FORBIDDEN).
errorobject requiredcodestring requiredmessagestring requiredrequest_idstring
429
Too many requests (RATE_LIMITED). Wait for Retry-After seconds.
Retry-AfterintegerSeconds to wait before retrying.
errorobject requiredcodestring requiredmessagestring requiredrequest_idstring
500
Something went wrong on EvoHub's side (INTERNAL_ERROR). Retry later.
errorobject requiredcodestring requiredmessagestring requiredrequest_idstring
Example request
curl -X GET 'https://evohub.io/api/v1/monitors/attention' \
-H 'Authorization: Bearer <TOKEN>'