Skip to main content
POST
List issues

Restrictions

Usage

  • start_time and end_time are millisecond timestamps. Maximum range: 183 days.
  • By default an issue matches when it was created inside the window; with by_intersection=true it matches when it was created before end_time and last seen at or after start_time.
  • Issues of private applications are excluded unless the caller is the account owner or an admin, created the application, or belongs to its team.
  • statuses filters by issue status. Valid values: for_review, reviewed, ignored, resolved.
  • orderby accepts: created_at, updated_at (default), session_count, error_count, severity. With severity, issues without a severity always sort last.
  • Use dql or sql for advanced filtering. Cannot provide both.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Filters for listing issues.

end_time
integer<int64>
required

End of the time range, Unix epoch milliseconds. Must be greater than start_time; maximum range: 183 days.

start_time
integer<int64>
required

Start of the time range, Unix timestamp in milliseconds (a value that looks like seconds is rejected). Issues are matched by creation time unless by_intersection is true.

application_ids
string[]

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

asc
boolean

Sort ascending when true; descending by default.

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.

dql
string

DQL query for advanced filtering. Field names must be fields of the issue scope (see POST /rum/field/list with scopes: ["issue"]); a bare full-text term searches the error message. Cannot be used with sql. A value list in a filter (field:(a OR b ...)) may hold at most 100 values.

error_required
boolean

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

limit
integer

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

Required range: 1 <= x <= 100
orderby
enum<string>

Sort field; defaults to updated_at when omitted.

Available options:
created_at,
updated_at,
session_count,
error_count,
severity
p
integer

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

Required range: x >= 1
sql
string

SQL-style WHERE condition for advanced filtering, without the WHERE keyword (for example error_count > 100). Field names must be fields of the issue scope; any text containing SELECT is rejected. Cannot be used with dql. A value list in a filter (field IN (...)) may hold at most 100 values.

statuses
enum<string>[]

Filter by triage status; any other value is rejected with a parameter error.

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

Filter by suspected cause category.

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.

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

Operation-specific payload, documented in each operation's 200 response. Operations without a payload return {} or omit data entirely.