Uptimeify Docs
Incident management

Escalate Incident Now

Skips the wait and pages the next escalation tier of a triggered Incident Management incident immediately.

POST /api/im/incidents/:id/escalate-now

Pages the next escalation tier of the incident's team right away instead of waiting for the current tier's timeout. Only valid while the incident is triggered (still escalating). The pending jobs of the current tier are cancelled and the next tier (the lowest tier order above the current one) is armed immediately. The tier change itself is applied by the escalation engine moments later, so currentTier in the response still shows the tier you escalated from.

Authentication

Any IM-eligible role (admin, editor, responder) or an organization-wide API token, see Authentication. Incident Management must be enabled for the organization.

Restricted to the incident's team: you must be a member of the incident's team (teamId) or an organization admin. An organization-wide API token passes as an organization admin.

No request body.

Example (cURL)

curl -X POST "$BASE_URL/api/im/incidents/42/escalate-now" \
  -H "Authorization: Bearer $TOKEN"

Response

200 OK: the updated incident row (same shape as the items of List Incidents, without the enrichment fields).

{
  "id": 42,
  "teamId": 3,
  "title": "Database connection pool exhausted",
  "severity": "sev1",
  "status": "triggered",
  "currentTier": 1,
  "escalationEpoch": 3
}

(Shortened; the full row is returned.)

Common errors

  • 401 Unauthorized when not authenticated
  • 403 Forbidden (customerScopedTokenForbidden) when using a customer-scoped token
  • 403 Forbidden (imAccessDenied) when the session user has no IM-eligible role
  • 403 Forbidden (imNotEnabled) when Incident Management is not enabled for the organization
  • 403 Forbidden (imTeamMembershipRequired) when you are neither a member of the incident's team nor an organization admin
  • 400 Bad Request (invalidRequestBody) when :id is not a positive integer
  • 404 Not Found (imIncidentNotFound) when the incident does not exist, or belongs to another organization
  • 422 Unprocessable Entity (imIncidentNotEscalating) when the incident is not triggered
  • 422 Unprocessable Entity (imNoFurtherTier) when the team has no tier above the current one
  • 409 Conflict (imIncidentStatusConflict) when the incident's escalation state changed concurrently, safe to retry

On this page