Skip to main content
POST
/
incident
/
war-room
/
default-observers
Get war-room default observers
curl --request POST \
  --url 'https://api.flashcat.cloud/incident/war-room/default-observers?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "incident_id": "664a1b2c3d4e5f6a7b8c9d0e"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "observers": [
      {
        "account_id": 10001,
        "person_id": 20001,
        "person_name": "Alice Chen",
        "avatar": "https://cdn.flashcat.cloud/avatar/20001.png",
        "email": "alice@acme.com",
        "phone": "+8613800000000",
        "locale": "zh-CN",
        "time_zone": "Asia/Shanghai",
        "as": "responder",
        "status": "active"
      }
    ]
  }
}

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsNone — 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
​
incident_id
string
required

Incident ID, a MongoDB ObjectID hex string.

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

Endpoint-specific payload. See each operation's 200 response schema.