Skip to main content
POST
Create war room

Restrictions

Usage

  • Requires the Professional edition or higher; otherwise the call fails with NoLicense.
  • The IM integration must be enabled with war room turned on. Feishu, DingTalk, WeCom (self-built app only), and Slack are supported.
  • An incident can have only one war room. Calling again with the same integration_id returns the existing group (with an empty share_link); a different integration_id fails with InvalidParameter.
  • A concurrent creation for the same incident returns RequestTooFrequently.
  • A successful creation adds an i_wr_create timeline entry.

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 opening an incident war room in an IM integration.

incident_id
string
required

Incident ID (MongoDB ObjectID).

Pattern: ^[0-9a-fA-F]{24}$
integration_id
integer<int64>
required

IM integration ID with war room enabled; obtain it from POST /datasource/im/war-room-enabled/list. Feishu, DingTalk, WeCom (self-built app only), and Slack are supported.

member_ids
integer<int64>[]

Member IDs to invite into the group; every ID must be a valid member of the account.

add_observers
boolean

When true, also invite members who were assigned or added as responders earlier but are no longer current responders.

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

War room group details read from the IM platform. When the IM lookup fails (for example, the group was dissolved outside Flashduty), all fields are empty strings.