Skip to main content
POST
Merge alerts into an incident

Restrictions

Usage

  • Every alert_ids entry and the incident_id must belong to the account; an unknown ID returns InvalidParameter.
  • Alerts already in the target incident are skipped. A source incident left with no alerts is closed.
  • title and owner_id update the target incident only when they differ from its current values.

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
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. At most 100 items per request; split larger sets into several calls.

Maximum array length: 100
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

An empty object. Returned as the data payload by operations whose success signal is simply the absence of an error.