History your accountants can read

Transaction history exports per tenant — CSV from the dashboard, the API for pipelines

Transaction history exports as CSV, per vault and per period, and the same records are available over the API for reconciliation and for your auditors' own tooling. The history is append-only and retained indefinitely, so the export you pull next year describes the same movements as the one you pull today.

Share the Trust, Guard the Keys

Create accountLive on testnet in an afternoon

Compare PlansIncluded in a plan, not an add-on

The problem

A month-end reconstruction is not a report

Screenshots, a block explorer and a group chat are how reconciliation becomes archaeology. Vaultody records each transaction request as it happens — its policy evaluation, who approved it, when it broadcast, when it mined — and hands it over in a form your finance and compliance functions can read without you in the room.

Per tenant, per vault, per periodCSV transaction exports scope to a vault and a period, so closing a month is a pull rather than a reconstruction.
The structure does the groupingVault accounts partition a vault by purpose, desk or customer, so per-customer and per-desk reporting falls out of the hierarchy.
Nothing expires quietlyTransaction and operational logs are retained indefinitely — there is no scheduled purge to plan a retention policy around.

How it works

Pull it, or let your pipeline pull it

The dashboard exports CSV for people. The API serves the same records to systems, so a reporting pipeline reads them directly instead of scraping a screen. Both read one append-only history, and both value assets from the same normalized chain-asset catalog.

✓CSV transaction exports per vault and per period, from the dashboard
✓API access to the same records, per tenant, for reconciliation and audit tooling
✓Each record carries its policy evaluation, its approvers and its on-chain milestones
✓Internal transfers between accounts of one vault carry the same audit treatment as on-chain sends

Specification

What you can pull

Plus the one place the coverage is still thin.

Transaction historyCSV export per vault and per period, and the same records over the API.

Per recordCreation, policy evaluation, each approval, broadcast and mining — with timestamps.

ScopePer tenant. Vault accounts partition a vault by purpose, desk or customer, and addresses hang off accounts.

Internal movementsTransfers between accounts of one vault are ledger movements with full audit treatment and their own webhook event.

Access historyLogin history including source address and device metadata.

Delivery evidenceCallback logs record what was sent to your endpoint and what it answered.

ValuationBalances read one normalized chain-asset catalog with exchange-rate endpoints, so the dashboard and the API do not drift apart.

RetentionTransaction and operational logs are retained indefinitely; API request statistics are a rolling window of roughly 90 days.

Honest gapA single unified log of every dashboard administrative action is not complete today; transaction, access and delivery evidence are.

Frequently asked questions

Get answers to commonly asked questions.

What form do exports take?

CSV from the dashboard, per vault and per period. The API serves the same records for reporting pipelines and for your auditors' own tooling.

How far back can we pull?

Transaction and operational logs are retained indefinitely — no scheduled purge. API request statistics are the exception, on a rolling window of roughly 90 days.

Which plans include it?

The audit trail and its exports are on every plan. API requests are included from Standard.