Skip to main content
POST
Merge alerts into an incident

Restrictions

Usage

  • All alert_ids and the incident_id must belong to the caller’s account.
  • Optionally set title and owner_id to update the target incident at the same time.

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
alert_ids
string[]
required

Alert IDs to merge (ObjectID hex strings); obtain them from POST /alert/list. Every ID must belong to the caller's account.

Minimum array length: 1
incident_id
string
required

Target incident ID (ObjectID hex string); obtain it from POST /incident/list.

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

Optional comment recorded on the merge feed entry. At most 1024 characters.

Maximum string length: 1024
title
string

Optional new title for the target incident. At most 512 characters.

Maximum string length: 512
owner_id
integer<int64>

Member ID of the new owner for the target incident; obtain it from POST /member/list.

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.