Find the Incident for a Monitoring Incident
Resolves a monitoring incident id to the Incident Management incident it was bridged into.
GET /api/im/incidents/by-monitor/:id
When the monitoring bridge is on (see organization settings), every incident from Uptimeify's own monitoring becomes an alert in Incident Management, grouped into an incident. This endpoint answers which Incident Management incident a given monitoring incident ended up in, for example to link from a monitoring incident to its paging and timeline.
Only alerts of the organization's own monitoring source count. A custom webhook that happens to send the same dedup key (monitor:<id>) is never matched. When the monitoring incident was bridged several times, the newest alert wins.
Authentication
Any IM-eligible role (admin, editor, responder) or an organization-wide API token, see Authentication. Incident Management must be enabled for the organization.
Path parameters
| Parameter | Type | Description |
|---|---|---|
id | number | The id of the monitoring incident, as returned by List Incidents of the monitoring API. |
Example (cURL)
curl -X GET "$BASE_URL/api/im/incidents/by-monitor/5123" \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/json"Response
{
"incidentId": 1834
}Load the incident itself with Get Incident.
Common errors
400 Bad Request(invalidRequestBody) whenidis not a positive number401 Unauthorizedwhen not authenticated403 Forbidden(customerScopedTokenForbidden) when using a customer-scoped token403 Forbidden(imAccessDenied) when the caller has no IM-eligible role403 Forbidden(imNotEnabled) when Incident Management is not enabled for the organization404 Not Found(imIncidentNotFound) when the monitoring incident was not bridged (yet), or belongs to another organization
Get Incident
Returns the full detail of a single Incident Management incident: the incident row plus its alerts, timeline events, and role assignments.
Create Incident
Manually creates an Incident Management incident for a team; escalation arms moments after creation, with the same paging behavior as an alert-sourced incident.