List issues
Return a paginated list of RUM error tracking issues matching the given filters.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | None — any valid app_key can call this operation |
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 time range, millisecond timestamp.
End of time range, millisecond timestamp. Maximum range: 183 days.
Filter by application IDs.
DQL query for advanced filtering. Cannot be used with sql.
SQL-style query for advanced filtering. Cannot be used with dql.
Filter by statuses.
for_review, reviewed, ignored, resolved Filter by suspected causes.
Filter by team IDs.
Page number. Default: 1.
Page size. Range: 1–100. Default: 20.
created_at, updated_at, session_count, error_count If true, only return issues with at least one associated error event.
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.