Skip to main content

List Audit Logs

Returns a paginated list of audit log entries, newest first. You can filter by action type and resource type.

Who sees details

details records what changed: before and after values, names, and addresses. It is always sanitised. Values under credential-shaped keys (client_secret, access_token, and so on) read ***REDACTED***, and user:password@ userinfo is removed from any URL. Identifiers are kept, such as the acting key’s api_key_id. The rest of the row (action, resource, IP address and time) is returned to every caller. A redacted details is always an empty object, never a string, so typed clients decode it unchanged. details itself is always an object or null: an entry whose stored details are not a JSON object (a bare string, array or number from a self-hosted agent) is returned sanitised and wrapped as {"value": ...}. The same rule applies to GET /v1/audit-logs/events and to the dashboard’s Audit Trail.

Query Parameters

Response

Common Action Types

Standard CRUD actions appear on any resource type: Critical audit chain actions — these go into the separate audit_log_critical table (see below):

Common Resource Types

General audit log resource types: Critical audit chain resource types (see audit_log_critical below):
Audit log entries are immutable and cannot be modified, but they are pruned according to your subscription plan’s data retention policy — a scheduled cleanup deletes audit_logs rows older than the plan’s retention window. The separate critical audit chain (audit_log_critical, see chain below) is never pruned and is retained permanently.