Export issues as CSV
Export the filtered RUM error tracking issues as a CSV file. The response is a text/csv stream delivered with Content-Disposition: attachment — it is not a JSON envelope; non-console callers can read the X-Export-Total and X-Export-Truncated response headers.
Restrictions
Usage
- The response is a
text/csvstream delivered withContent-Disposition: attachment— it is not wrapped in the standard envelope. The filename isrum-issues-<timestamp>.csv, stamped in the requestedtime_zone. ReadX-Export-TotalandX-Export-Truncatedresponse headers instead of a body field. - The export reads the first 100 matching rows (
ExportMaxRows);X-Export-Truncatedistruewhen more issues match.pandlimitare ignored. - The request filters are exactly those of
POST /rum/issue/list— an export is “what I am looking at, as a file”. export_fieldsnames the CSV columns in the order they appear. Unknown keys are rejected with a parameter error; an empty array uses the default column set.time_zonemust be a valid IANA zone name (e.g.Asia/Shanghai,UTC); timestamps are rendered in that zone and time columns carry the zone in their header. Invalid names are rejected.console_originis used to build theissue_urlcolumn; the service cannot infer it (SaaS, on-premises and dev releases answer on different origins).- Every call is recorded in the account’s audit log with the caller’s member ID, request payload, and resulting error (if any). Do not put secrets in request fields.
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 exporting RUM error tracking issues to CSV.
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). Ignored by the export — the first 100 matching rows are always read.
Page size (1–100). Ignored by the export — the row cap is fixed at 100.
Sort field; defaults to updated_at when omitted.
created_at, updated_at, session_count, error_count, severity Sort ascending when true; descending by default.
If true, only export issues with at least one associated error event.
When true, match by time-range overlap: export issues still active within the window (last_seen_timestamp >= start_time) even if created before it. Default false exports only issues created inside the window.
CSV columns to export, in the order they appear. Unknown keys are rejected with a parameter error; an empty array uses the default column set.
issue_id, issue_url, application_name, service, error_type, error_message, status, severity, is_crash, error_count, session_count, first_seen_at, first_seen_version, last_seen_at, last_seen_version, versions, suspected_cause, resolved_at Console origin used to build the issue_url column, e.g. https://console.flashcat.cloud. The service cannot infer it (SaaS, on-premises and dev releases answer on different origins).
IANA time zone used to render timestamps in the CSV, e.g. Asia/Shanghai or UTC. Default: Asia/Shanghai.
Response
Success. CSV attachment, not a JSON envelope.
CSV file content. The header row matches the exported columns in order; values are sanitized against spreadsheet formula injection.