Skip to main content
Create and read incidents. Incidents are a core resource, on which many other resources (actions, etc) are created. Care should be taken around these endpoints, as automation that creates duplicate incidents can be distracting, and impact reporting.

The incident object

created_at
string<date-time>
required

When the incident was created

Example:

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

creator
object
required
Example:
custom_field_entries
object[]
required

Custom field entries for this incident

Example:
id
string
required

Unique identifier for the incident

Example:

"01FDAG4SAP5TYPT98WGR2N7W91"

incident_role_assignments
object[]
required

A list of who is assigned to each role for this incident

Example:
incident_status
object
required
Example:
mode
enum<string>
required

Whether the incident is real, a test, a tutorial, or importing as a retrospective incident

Available options:
standard,
retrospective,
test,
tutorial
Example:

"standard"

name
string
required

Explanation of the incident

Example:

"Our database is sad"

reference
string
required

Reference to this incident, as displayed across the product

Example:

"INC-123"

slack_channel_id
string
required

ID of the Slack channel in the organisation Slack workspace. Note that the channel is sometimes created asynchronously, so may not be present when the incident is just created.

Example:

"C02AW36C1M5"

slack_team_id
string
required

ID of the Slack team / workspace. This is only required if you are using a Slack Enterprise Grid with multiple teams.

Example:

"T02A1FSLE8J"

updated_at
string<date-time>
required

When the incident was last updated

Example:

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

visibility
enum<string>
required

Whether the incident should be open to anyone in your Slack workspace (public), or invite-only (private). For more information on Private Incidents see our docs.

Available options:
public,
private
Example:

"public"

call_url
string

The call URL attached to this incident

Example:

"https://zoom.us/foo"

duration_metrics
object[]

Incident duration metrics and their measurements for this incident

Example:
external_issue_reference
object
Example:
has_debrief
boolean

If this incident has a debrief attached

Example:

false

incident_timestamp_values
object[]

Incident lifecycle events and when they occurred

Example:
incident_type
object
Example:

A permanent link to the homepage for this incident

Example:

"https://app.incident.io/incidents/123"

postmortem_document_ids
string[]

An array of IDs of postmortem documents for this incident

Example:
postmortem_document_url
string

The URL of the incident post-mortem document

Example:

"https://docs.google.com/my_doc_id"

severity
object
Example:
slack_channel_name
string

Name of the slack channel

Example:

"inc-165-green-parrot"

summary
string

Detailed description of the incident

Example:

"Our database is really really sad, and we don't know why yet."

workload_minutes_late
number<double>

Amount of time spent on the incident in late hours

Example:

40.7

workload_minutes_sleeping
number<double>

Amount of time spent on the incident in sleeping hours

Example:

0

workload_minutes_total
number<double>

Amount of time spent on the incident in total

Example:

60.7

workload_minutes_working
number<double>

Amount of time spent on the incident in working hours

Example:

20