Skip to main content
POST
List raw alert events

Restrictions

Usage

  • Results are filtered by the caller’s channel data-access permissions.
  • severities is a comma-separated string, e.g. "Critical,Warning".

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

Filter and pagination criteria for the global raw event list.

start_time
integer<int64>

Start of search window, Unix epoch seconds.

end_time
integer<int64>

End of search window, Unix epoch seconds.

p
integer<int64>

Page number, starting at 1. Used when search_after_ctx is not provided.

limit
integer<int64>

Page size, max 100, default 20.

search_after_ctx
string

Opaque cursor for the next page.

integration_ids
integer<int64>[]

Filter by integration IDs.

integration_types
string[]

Filter by integration types (plugin keys).

channel_ids
integer<int64>[]

Filter by channel IDs. Max 100.

severities
string

Comma-separated severity filter, e.g. Critical,Warning.

orderby
enum<string>

Sort field (ES field name).

Available options:
event_time
asc
boolean

Sort ascending when true.

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.