Reopen incident

Reopen a previously resolved incident.

POST /incident/reopen

Reopen incident

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/incident/reopen?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "incident_ids": [
    "69da451ef77b1b51f40e83ee"
  ],
  "reason": "Monitoring detected the issue recurred after the initial fix."
}
'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Incidents 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 reopening one or more closed incidents.

incident_ids · string[] · required

Incident IDs to reopen. At most 100 per call.

Required array length: 1 - 100 elements

Pattern: ^[0-9a-fA-F]{24}$

reason · string

Optional reason recorded on the timeline.

Maximum string length: 1024

Response

200

application/json

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.