Search audit logs
Return a cursor-paginated list of audit log entries within a time range.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Audit Read (organization) |
Usage
- Time range is required. Maximum span is 90 days. Both
start_timeandend_timeare Unix epoch seconds. - Use
search_after_ctxfrom the previous response to fetch the next page. The token is opaque — do not construct it manually. - The retention window depends on the account’s license. Queries beyond the retention boundary silently return an empty result rather than an error.
- Default page size is 20 rows; maximum is 99.
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
Filter criteria for audit log search. Time range is required.
Start of the search window, Unix epoch seconds.
1712620800
End of the search window, Unix epoch seconds. Must be after start_time. Maximum span 90 days.
1712707200
Page size. Minimum 0, maximum 99.
0 <= x <= 9920
Filter to a single request by its unique request ID.
Opaque pagination cursor returned by the previous response. Leave empty for the first page.
Filter to specific operation names. Use POST /audit/operation/list to get the valid set.
Filter by the member who performed the action.
When true, return only high-risk (dangerous) operations.
When true, return only write operations; when false, return only read operations.
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.