Overview

Audit logs provide a chronological record of state-changing actions and operations in Institutional Vault. They support compliance review, accountability, and troubleshooting.

Export Audit Logs

Open Settings from the main navigation.
Select the Audit Logs tab.
Choose a Date Range. The picker allows dates within the last year.
Optionally filter by Operation ID or Transaction ID(s) (comma-separated).
Under Download format, choose:
- Auditor view (.csv) - default flat-column CSV, one row per operation after lifecycle merge, plus non-operation events such as login.
- Full forensics (.zip) - raw-JSON metadata CSV inside a ZIP, with every audit entry and a full Metadata column for programmatic inspection.
Click Export.

The settings page also shows a Recent audit events preview (same column set as the auditor CSV, limited to the most recent entries).

📘
Note:
Prefer Auditor view for Excel or Google Sheets. Use Full forensics when you need the complete intent payload (for example with jq).

Auditor CSV columns

Column	Description
Date	Event timestamp (RFC 3339, UTC).
Operation ID	Vault operation identifier for operation-bound rows; empty for non-operation events.
Event Name	Audit event name (for example `transaction.create` or an MPA lifecycle event).
Operation Type	Operation type when the row is bound to an operation.
Function	On-chain or parsed function name when available (for example mint, burn, transfer).
Amount	Per-destination amount(s); multiple values joined with `;` .
Token	Asset symbol or token name.
CAIP-2	Chain identifier derived from the operation intent (for example `eip155:1`).
Source Wallet	Source account name and on-chain address.
Destination Wallet	Destination account name(s) and address(es); multiple values joined with `;` .
Operation Status	Human-readable status (for example Finished, Pending Approval, Rejected).
Initiator	Email of the user who initiated the operation, or actor email for non-operation events.
Approved By	Approver emails, joined with `;` .
Rejected By	Rejector emails, joined with `;` .
Error Code	Error code when the operation failed.
Error Message	Error message when the operation failed.

📘
Note:
Auditor view merges lifecycle entries for the same operation into one row. If an operation was created outside the selected date range, detail cells such as amount or wallets can appear blank. Widen the range to include creation, or use Full forensics for every raw entry.

API export

Programmatic export uses:

GET /api/v2/audit-logs/download - download. Query parameters include start_date and end_date (required, RFC 3339), optional operation_id, transaction_id, and format (summary default, or forensics-zip).
GET /api/v2/audit-logs - recent entries for the settings preview (same summary columns; not for deep historical browsing).

Default summary responses are text/csv (audit_logs.csv). forensics-zip returns application/zip (audit-logs-forensics.zip).

See the Audit Logs API reference and your deployment Swagger UI for request details.

🗣️We Are Here to Help!

Please contact us via email or support chat if you encounter an issue, bug, or need assistance. Don't forget to include any relevant details about the problem. To request a wallet form and Institutional Vault Approver form, please click here or contact our sales team.