Skip to main content
POST
/
alert
/
merge
Merge alerts into an incident
curl --request POST \
  --url 'https://api.flashcat.cloud/alert/merge?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "alert_ids": [
    "663a1b2c3d4e5f6789abcdef"
  ],
  "incident_id": "663a000000000000deadbeef"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsChannels Read (on-call)

​
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.

​
incident_id
string
required

Target incident ID.

​
comment
string

Optional comment on the merge action.

​
title
string

Optional new title for the target incident.

​
owner_id
integer<int64>

Optional new owner for the target incident.

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.