List issues
Return a paginated list of RUM error tracking issues matching the given filters.
Restrictions
Usage
start_timeandend_timeare millisecond timestamps. Maximum range: 183 days.statusesfilters by issue status. Valid values:for_review,reviewed,ignored,resolved.orderbyaccepts:created_at,updated_at,session_count,error_count.- Use
dqlorsqlfor advanced filtering. Cannot provide both.
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
Filters for listing issues.
Start of the time range, Unix epoch milliseconds.
End of time range, millisecond timestamp. Maximum range: 183 days.
Filter by application IDs. Get IDs via POST /rum/application/list.
DQL query for advanced filtering. Cannot be used with sql.
SQL-style query for advanced filtering. Cannot be used with dql.
Filter by status; only the enum values are accepted — any other value is rejected with a parameter error.
for_review, reviewed, ignored, resolved Filter by suspected cause; see the enum for valid values.
api.failed_request, network.error, code.exception, code.invalid_object_access, code.invalid_argument, unknown Filter by team IDs. Get team IDs via POST /team/list.
Page number (1-based). Default: 1.
Page size. Range: 1–100. Default: 20.
Sort field; defaults to updated_at when omitted.
created_at, updated_at, session_count, error_count Sort ascending when true; descending by default.
If true, only return issues with at least one associated error event.
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.