Add war-room member

Add one or more members to the IM war room bound to an incident integration.

POST /incident/war-room/add-member

Add war-room member

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/incident/war-room/add-member?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "integration_id": 362,
  "chat_id": "oc_5ce6d572455d361153b7cb51da133945",
  "member_ids": [
    20001,
    20002
  ]
}
'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": "ok"
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	None — any valid app_key can call this operation

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

integration_id · integer<int64> · required

IM integration that hosts the war room.

chat_id · string · required

Chat ID of the war room within the IM platform.

member_ids · integer<int64>[] · required

Person IDs to add to the war room.

Response

200

application/json

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 · string · required

Returns the literal "ok" on success.