Skip to main content
POST
List alert activity feed

Restrictions

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. a_comm, a_merge).
  • An alert_id not found in the account returns InvalidParameter.

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

Alert ID (ObjectID hex string); obtain it from POST /alert/list.

Pattern: ^[0-9a-fA-F]{24}$
p
integer<int64>
default:1

Page number, starting at 1.

Required range: x >= 1
limit
integer<int64>

Page size, max 100, default 20.

Required range: 1 <= x <= 100
asc
boolean

Sort ascending.

types
string[]

Filter by feed type codes — see the type field of the response items for the full list (e.g. a_new, a_comm, a_merge).

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

Operation-specific payload, documented in each operation's 200 response. Operations without a payload return {} or omit data entirely.