Skip to main content
POST
List incidents by IDs

Restrictions

Usage

  • IDs that do not match an incident are omitted; total is the number of incidents found and has_next_page is always false.
  • Results are sorted by start_time, newest first.
  • This endpoint does not fill integration_type or assigned_to.escalate_rule_name.

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

Batch lookup parameters for incidents.

incident_ids
string[]
required

Incident IDs to query, at most 100 per call; obtain them from POST /incident/list.

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

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

Paginated list of incidents.