Skip to main content
POST
Merge incidents

Restrictions

Usage

  • All alerts of the source incidents move to the target incident, and the target gains the sources’ integrations.
  • Source incidents that are still open are closed. With remove_source_incidents: true they are then permanently deleted; otherwise they stay closed with an i_merge timeline entry that points to the target.
  • The target’s progress, responders, and assignment do not change; title, when set, replaces the target’s title.

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 merging source incidents into a target.

source_incident_ids
string[]
required

Source incident IDs. The target incident is removed from this set automatically.

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

Target incident ID of the merge; obtain it from POST /incident/list.

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

Optional new title for the target incident.

Maximum string length: 512
comment
string

Optional comment recorded on the merge timeline entry.

Maximum string length: 1024
owner_id
integer<int64>

Accepted for compatibility but currently ignored by the server; the merge does not change the target incident owner.

remove_source_incidents
boolean

When true, permanently delete the source incidents after their alerts move to the target. When false, the sources are closed and kept.

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.