Skip to main content
POST
/
alert
/
feed
List alert activity feed
curl --request POST \
  --url 'https://api.flashcat.cloud/alert/feed?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "alert_id": "663a1b2c3d4e5f6789abcdef",
  "limit": 20,
  "asc": false
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "has_next_page": false,
    "items": [
      {
        "ref_id": "663a1b2c3d4e5f6789abcdef",
        "type": "alert_comment",
        "detail": {
          "comment": "Investigating now."
        },
        "creator_id": 80011,
        "created_at": 1712651000
      }
    ]
  }
}

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

  • Use p (page number, starting at 1) and limit (max 100, default 20) for pagination.
  • Set asc to true for chronological order.
  • Use types to filter by specific feed types (e.g. alert_comment, alert_merge).

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.

​
p
integer<int64>
default:1

Page number, starting at 1.

​
limit
integer<int64>

Page size, max 100, default 20.

​
asc
boolean

Sort ascending.

​
types
string[]

Filter by feed types.

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.