Skip to main content
POST
Add war-room member

Restrictions

Usage

  • Requires the On-call Pro license.
  • chat_id must identify a war room created through Flashduty on integration integration_id; otherwise the call returns ResourceNotFound.
  • Only Feishu (Lark), DingTalk, WeCom and Slack integrations support war rooms; other integrations return InvalidParameter.
  • Every ID in member_ids must be a person in the account; one unknown ID fails the whole request.
  • On success data is the string ok.

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
integration_id
integer<int64>
required

ID of the IM integration hosting the war room; obtain it from POST /datasource/im/war-room-enabled/list.

chat_id
string
required

Chat ID of the war-room group on the IM platform, as returned for the war room by POST /incident/war-room/list.

member_ids
integer<int64>[]
required

Person IDs (member IDs, or the account ID for the owner) to add. Must not be empty.

Minimum array length: 1

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
string

Returns the literal "ok" on success.