Query a paginated list of incidents with filters by channel, severity, status, responder, and time range.
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.
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Incidents Read (on-call) |
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.
Filters for the incident list query. start_time and end_time are required; the window must not exceed 31 days.
Window start, Unix seconds.
Window end, Unix seconds. Must be greater than start_time and within 31 days.
Ascending order when true.
When true, include only snoozed incidents.
When true, restrict to incidents in channels owned by the user's teams.
When true, restrict to incidents in channels the user personally owns.
When true, include only incidents that were ever silenced.
When true, include only outlier (rare) incidents.
Comma-separated list of progress states to match (e.g. Triggered,Processing).
Full-text search query.
Comma-separated list of severities (Critical,Warning,Info).
Channel IDs to filter by. Use 0 for standalone (global) incidents.
Team IDs; resolved to channels via channel ownership.
Responder member IDs.
Acknowledger member IDs.
Creator member IDs. Use 0 for automatically created incidents.
Closer member IDs. Use 0 for automatically closed incidents.
Restrict to the given incident IDs.
Restrict to the given short display identifiers.
Page number starting at 1.
x >= 0Page size, at most 100.
0 <= x <= 100Cursor from a previous response for forward pagination.
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.