Skip to main content
POST
/
incident
/
create
Create incident
curl --request POST \
  --url 'https://api.flashcat.cloud/incident/create?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "incident_severity": "Critical",
  "title": "Database connection timeout on prod-db-01",
  "channel_id": 2551105804131,
  "assigned_to": {
    "person_ids": [
      2476444212131
    ]
  }
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "incident_id": "69db2ef1a0fe7db6448b14f1",
    "title": "API test incident for docs"
  }
}

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsIncidents Manage (on-call)

Authorizations

​
app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Parameters for manually creating an incident.

​
incident_severity
enum<string>
required

Incident severity.

Available options:
Info,
Warning,
Critical
​
title
string

Incident title, up to 512 characters.

Maximum string length: 512
​
description
string

Incident description, up to 1024 characters.

Maximum string length: 1024
​
channel_id
integer<int64>

Channel to file the incident into. Optional; leave unset for a standalone incident.

​
assigned_to
object

Incident assignment target. Either person_ids or escalate_rule_id must be provided.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

​
request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

​
data
object
required

Result of manually creating an incident.