Skip to main content
POST
/
v1
/
incident_statuses
Create
curl --request POST \
  --url https://api.incident.io/v1/incident_statuses \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data @- <<EOF
{
  "category": "live",
  "description": "Impact has been **fully mitigated**, and we're ready to learn from this incident.",
  "name": "Closed"
}
EOF
{
  "incident_status": {
    "category": "triage",
    "created_at": "2021-08-17T13:28:57.801578Z",
    "description": "Impact has been **fully mitigated**, and we're ready to learn from this incident.",
    "id": "01FCNDV6P870EA6S7TK1DSYD5H",
    "name": "Closed",
    "rank": 4,
    "updated_at": "2021-08-17T13:28:57.801578Z"
  }
}

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.

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"

Response

201 - application/json

Created response.

​
incident_status
object
required