Skip to main content
POST
Search audit logs

Restrictions

Usage

  • Time range is required. Maximum span is 90 days. Both start_time and end_time are Unix epoch seconds.
  • Use search_after_ctx from 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.
  • Pass an explicit limit (1–99) for predictable paging; when it is omitted or 0 the server chooses the page size, which may be the whole result set. Entries are returned newest first.

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

Filter criteria for audit log search. Time range is required.

start_time
integer<int64>
required

Start of the search window, Unix epoch seconds. Exclusive — entries at exactly this second are not included.

Required range: x >= 1
Example:

1712620800

end_time
integer<int64>
required

End of the search window, Unix epoch seconds. Inclusive. Must be after start_time; maximum span 90 days.

Required range: x >= 1
Example:

1712707200

limit
integer

Page size, 0–99. Omit or set to 0 to let the server choose the page size (it may return every matching entry).

Required range: 0 <= x <= 99
Example:

20

request_id
string

Filter to a single request by its unique request ID.

search_after_ctx
string

Opaque pagination cursor returned by the previous response. Leave empty for the first page.

operations
string[]

Filter to specific operation names. Use POST /audit/operation/list to get the valid set.

person_id
integer<uint64>

Filter by the operator's member ID (get IDs from POST /member/list). Pass the account ID to match actions performed by the account principal itself.

is_dangerous
boolean | null

When true, return only high-risk (dangerous) operations.

is_write
boolean | null

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.

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

Cursor-paginated audit log search result.