Skip to main content
POST
/
incident
/
resolve
Resolve incident
curl --request POST \
  --url 'https://api.flashcat.cloud/incident/resolve?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "incident_ids": [
    "69da451ef77b1b51f40e83ee"
  ],
  "root_cause": "Memory leak in the connection pool caused by a missing cleanup call.",
  "resolution": "Deployed hotfix v2.3.1 and restarted the affected service."
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

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

​
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 resolving one or more incidents.

​
incident_ids
string[]
required

Incident IDs to resolve. At most 100 per call.

Required array length: 1 - 100 elements
Pattern: ^[0-9a-fA-F]{24}$
​
root_cause
string

Optional root cause note applied to every resolved incident.

Maximum string length: 1024
​
resolution
string

Optional resolution note applied to every resolved incident.

Maximum string length: 1024

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

Empty response body. The server returns data: null on success.