Return a paginated list of RUM error tracking issues matching the given filters.
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 | None — any valid app_key can call this operation |
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.dql or sql for advanced filtering. Cannot provide both.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 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.
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.