Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.incident.io/llms.txt

Use this file to discover all available pages before exploring further.

View incident types. With incident types enabled, you can tailor your process to the situation you’re responding to with different custom fields and roles for each incident type.

​
The incident type object

​
create_in_triage
enum<string>
required

Whether incidents of this must always, or can optionally, be created in triage

Available options:
always,
optional
Example:

"always"

​
created_at
string<date-time>
required

When this resource was created

Example:

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

​
description
string
required

What is this incident type for?

Example:

"Customer facing production outages"

​
id
string
required

Unique identifier for this Incident Type

Example:

"01FCNDV6P870EA6S7TK1DSYDG0"

​
is_default
boolean
required

The default Incident Type is used when no other type is explicitly specified

Example:

false

​
name
string
required

The name of this Incident Type

Example:

"Production Outage"

​
private_incidents_only
boolean
required

Should all incidents created with this Incident Type be private?

Example:

false

​
updated_at
string<date-time>
required

When this resource was last updated

Example:

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