Skip to main content
POST
List issues

Restrictions

Usage

  • start_time and end_time are millisecond timestamps. Maximum range: 183 days.
  • statuses filters by issue status. Valid values: for_review, reviewed, ignored, resolved.
  • orderby accepts: created_at, updated_at, session_count, error_count.
  • Use dql or sql for advanced filtering. Cannot provide both.

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 listing issues.

start_time
integer<int64>
required

Start of the time range, Unix epoch milliseconds.

end_time
integer<int64>
required

End of time range, millisecond timestamp. Maximum range: 183 days.

application_ids
string[]

Filter by application IDs. Get IDs via POST /rum/application/list.

dql
string

DQL query for advanced filtering. Cannot be used with sql.

sql
string

SQL-style query for advanced filtering. Cannot be used with dql.

statuses
enum<string>[]

Filter by status; only the enum values are accepted — any other value is rejected with a parameter error.

Available options:
for_review,
reviewed,
ignored,
resolved
suspected_causes
enum<string>[]

Filter by suspected cause; see the enum for valid values.

Available options:
api.failed_request,
network.error,
code.exception,
code.invalid_object_access,
code.invalid_argument,
unknown
team_ids
integer<int64>[]

Filter by team IDs. Get team IDs via POST /team/list.

p
integer

Page number (1-based). Default: 1.

limit
integer

Page size. Range: 1–100. Default: 20.

orderby
enum<string>

Sort field; defaults to updated_at when omitted.

Available options:
created_at,
updated_at,
session_count,
error_count
asc
boolean

Sort ascending when true; descending by default.

error_required
boolean

If true, only return issues with at least one associated error event.

by_intersection
boolean

When true, match by time-range overlap: return issues still active within the window (last_seen_timestamp >= start_time) even if created before it. Default false returns only issues created inside the window.

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.