Count facet value distribution
Return the top N values for a facet field within a time range, sorted by occurrence count descending.
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
- Use
POST /rum/facet/listto discover availablefacet_keyvalues for each scope. - The
scopemust be one of:session,view,action,error,resource,long_task,vital,issue,sourcemap. - Pass
dqlto further filter events before counting. DQL syntax follows the RUM query language. - Pass
sqlwith a WHERE-clause only (no SELECT) for SQL-style filtering. - Default limit is 100; maximum is 100.
- Time range is required (
start_time/end_timein Unix epoch milliseconds). Maximum span is 31 days.
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
Parameters for counting facet value distribution.
RUM data scope to query.
session, view, action, error, resource, long_task, vital, issue, sourcemap The field key to count value distribution for.
Start of the time range, Unix epoch milliseconds.
1712620800000
End of the time range, Unix epoch milliseconds. Maximum 31-day span.
1712707200000
When set, filter events where facet_key equals this value before counting. Accepts string, number, or boolean.
RUM DQL filter expression applied before counting.
SQL WHERE clause (no SELECT) for additional filtering.
Maximum number of top values to return. Default 100, maximum 100.
x <= 100Response
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.