Skip to main content
POST
List incidents

Restrictions

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

Filters for the incident list query. start_time and end_time are required; the window must not exceed 31 days.

start_time
integer<int64>
required

Window start, Unix seconds.

end_time
integer<int64>
required

Window end, Unix seconds. Must be greater than start_time and within 31 days.

asc
boolean

Ascending order when true.

is_snoozed
boolean

When true, include only snoozed incidents.

is_my_team
boolean

When true, restrict to incidents in channels owned by the user's teams.

is_my_channel
boolean

When true, restrict to incidents in channels the user personally owns.

ever_muted
boolean

When true, include only incidents that were ever silenced.

is_rare
boolean

When true, include only outlier (rare) incidents.

progress
string

Comma-separated list of progress states to match (e.g. Triggered,Processing).

query
string

Full-text search query.

incident_severity
string

Comma-separated list of severities (Critical,Warning,Info).

channel_ids
integer<int64>[]

Channel IDs to filter by. Use 0 for standalone (global) incidents.

team_ids
integer<int64>[]

Team IDs; resolved to channels via channel ownership.

responder_ids
integer<int64>[]

Responder member IDs.

acker_ids
integer<int64>[]

Acknowledger member IDs.

creator_ids
integer<int64>[]

Creator member IDs. Use 0 for automatically created incidents.

closer_ids
integer<int64>[]

Closer member IDs. Use 0 for automatically closed incidents.

incident_ids
string[]

Restrict to the given incident IDs.

nums
string[]

Restrict to the given short display identifiers.

p
integer<int64>

Page number starting at 1.

Required range: x >= 0
limit
integer<int64>
default:20

Page size, at most 100.

Required range: 0 <= x <= 100
search_after_ctx
string

Cursor from a previous response for forward pagination.

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

Paginated list of incidents.