Skip to main content
POST
Delete war room

Restrictions

Usage

  • The war room record is removed first; a failure to dissolve the group on the IM side (for example, it was already dissolved) is ignored.
  • Succeeds without changes when the incident has no war room on that integration.
  • To only unlink a war room whose IM integration is disabled or deleted, set unlink_only: true and pass its chat_id. This mode is limited to account owners and admins, fails with InvalidParameter while the integration is enabled, and does not dissolve the group.
  • On success the response has no data field.

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 deleting an incident war room.

incident_id
string
required

Incident ID (MongoDB ObjectID).

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

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

When true, only remove the link between the incident and the war room without dissolving the group. Allowed only for account owners and admins, only when the IM integration is disabled or deleted, and requires chat_id.

chat_id
string

Chat ID of the war room to unlink, from POST /incident/war-room/list. Required when unlink_only is true and must match the current war room; ignored otherwise.

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.