Skip to main content
Create and manage escalation paths, and create, list and filter escalations. With incident.io On-call you can create escalation paths that describe how a page should be escalated to people and schedules.

The escalation object

created_at
string<date-time>
required

When this escalation was created

Example:

"2021-08-17T13:28:57.801578Z"

creator
object
required

The creator of this escalation. Can be a user, a workflow, or an alert. If the escalation came from a call route, this will be empty.

Example:
events
object[]
required

Events which describe the history of this escalation. Events include information about what users or channels were notified and what users acked.

Example:
id
string
required

Unique ID of the escalation

Example:

"01G0J1EXE7AXZ2C93K61WBPYEH"

priority
object
required

The priority associated with this escalation.

Example:

Alerts related to this escalation

Example:

Incidents related to this escalation

Example:
status
enum<string>
required

Status of the escalation

Available options:
pending,
triggered,
acked,
resolved,
expired,
cancelled,
snoozed,
delayed,
pending_repeat
Example:

"pending"

title
string
required

The title of this escalation

Example:

"Database CPU is high"

updated_at
string<date-time>
required

When this escalation was last updated

Example:

"2021-08-17T13:28:57.801578Z"

escalation_path_id
string

Unique identifier of the escalation path that the escalation was created from

Example:

"01G0J1EXE7AXZ2C93K61WBPYEH"