Skip to main content
POST
/
alert
/
event
/
list
List events for an alert
curl --request POST \
  --url 'https://api.flashcat.cloud/alert/event/list?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "alert_id": "663a1b2c3d4e5f6789abcdef"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "items": [
      {
        "event_id": "663a1b2c3d4e5f6789abc001",
        "alert_id": "663a1b2c3d4e5f6789abcdef",
        "title": "CPU usage > 90%",
        "event_severity": "Critical",
        "event_status": "Critical",
        "event_time": 1712650000,
        "labels": {
          "host": "web-01"
        }
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsChannels Read (on-call)

​
Usage

  • Each alert accumulates raw events from the integration. This endpoint exposes the raw event history for a given alert.

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
​
alert_id
string
required

Alert ID (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.