List alerts
Return a cursor-paginated list of alerts matching the given filters.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Channels Read (on-call) |
Usage
- Both
start_timeandend_timeare required Unix epoch seconds. Maximum span is 31 days. - Use
search_after_ctxfrom the previous response to fetch the next page. - Results are filtered by the caller’s channel data-access permissions.
- Set
is_activetotrueto retrieve only active (firing) alerts;falseto retrieve resolved alerts.
Authorizations
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
Filter and pagination criteria for alert list queries. Time range is required.
Start of the search window, Unix epoch seconds.
End of the search window, Unix epoch seconds. Max span 31 days.
Page number, starting at 1. Used when search_after_ctx is not provided.
Page size. Max 100, default 20.
Opaque cursor from the previous response for the next page.
Filter by active (true) or resolved (false) status.
Filter by whether the alert has ever been silenced.
Comma-separated severity filter, e.g. Critical,Warning. Allowed values: Critical, Warning, Info, Ok.
Filter by channel IDs.
Filter by integration IDs.
Filter to specific alert IDs (ObjectID hex strings).
Filter by alert deduplication keys.
Sort field.
created_at, updated_at Sort ascending when true. Default descending.
When true, the time range filter is applied on updated_at rather than start_time.
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.