Query RUM data
Run one or more SQL-style RUM data queries over a bounded time range.
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
- Send 1 to 10 queries in one request; each query
idbecomes a key in the response object. start_timeandend_timeare required Unix epoch milliseconds. The maximum time range is 31 days.- Use
format: tablefor tabular results, orformat: time_seriesfor bucketed time-series results. - For
time_series,intervaldefaults to 3600 seconds andmax_pointsdefaults to 1226 when omitted. search_after_ctxis returned by paginated table queries and can be sent back to continue scanning.
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
Batch of RUM data queries over a bounded time range.
Start of the query window, Unix epoch milliseconds.
1712620800000
End of the query window, Unix epoch milliseconds. Maximum 31-day span.
1712707200000
Queries to execute concurrently. 1 to 10 queries are allowed.
1 - 10 elementsResponse
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.