Skip to main content
POST
Reopen incident

Restrictions

Usage

  • Every incident must be Closed; otherwise the whole call fails with InvalidParameter.
  • Reopened incidents return to Triggered, with ack_time, close_time, closer_id, and every responder’s acknowledgement reset.
  • Each incident is reassigned to its previous assignment target starting at the first escalation level, with assigned_to.type set to reopen.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

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 free-text reason, recorded on the i_reopen timeline entry. At most 1,024 characters.

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.