Skip to main content
POST
List events for an alert

Restrictions

Usage

  • Results are newest-first by default. Set asc=true to read events oldest-first.
  • Use limit with search_after_ctx from the previous response to fetch the next page.
  • Classic page-number pagination is also supported with p, but p * limit must stay within 10,000 records.
  • Each alert can accumulate a large raw event history; prefer cursor pagination for hot alerts.

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 (MongoDB ObjectID).

Pattern: ^[0-9a-fA-F]{24}$
asc
boolean
default:false

When true, return events oldest-first. Defaults to newest-first.

limit
integer<int64>
default:20

Page size. Defaults to 20 and cannot exceed 100.

Required range: 0 <= x <= 100
p
integer<int64>
default:1

Page number starting at 1. Used when search_after_ctx is omitted.

Required range: x >= 0
search_after_ctx
string

Cursor returned by the previous page. When supplied, cursor pagination is used instead of page-number pagination.

Pattern: ^[0-9a-fA-F]{24}$

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.