Skip to main content
POST
Create
🔑 Requires the incident_lifecycles.update scope.

Authorizations

Authorization
string
header
required

API key from your incident.io dashboard (Settings → API keys)

Body

application/json
category
enum<string>
required

Whether the status should be considered 'live' (now renamed to active), 'learning' (now renamed to post-incident) or 'closed'. The triage and declined statuses cannot be created or modified.

Available options:
live,
learning,
closed
Example:

"live"

description
string
required

Rich text description of the incident status

Example:

"Impact has been **fully mitigated**, and we're ready to learn from this incident."

name
string
required

Unique name of this status

Example:

"Closed"

rank
integer<int64>

Where this status sits within its category, lowest rank first. No two statuses in the same category can share a rank, but ranks needn't run consecutively — leaving gaps (10, 20, 30) means you can later insert a status between two others without renumbering them. Omit it to add this status to the end of its category.

Example:

4

Response

Created response.

incident_status
object
required