Skip to main content
GET
Every vault transaction the backend has recorded: deposits, redemptions, the operator’s own actions and the distributor fee flows. Each row was either confirmed from its receipt or recovered from the vault’s own events.
What you see depends on whose vault it is. On your own vault this is the full ledger, every action by every wallet. On a vault another operator runs it is one wallet’s own deposits and redemptions and nothing else, and address is what names that wallet. Without a valid address, transactions on someone else’s vault comes back as an empty array rather than an error.

Path Parameters

string
required
Vault ID.

Query Parameters

integer
default:"50"
Rows to return, newest first. Clamped to 1 to 200. A value that does not parse as an integer, or 0, falls back to 50.
integer
default:"0"
Rows to skip, newest first. Page with offset until hasMore is false.
string
Wallet whose rows to return. Ignored on your own vault, where the whole ledger is served. Required to see anything on a vault you do not operate.

Response Fields

array
integer
Rows in scope across every page: the whole ledger on your own vault, the named wallet’s deposits and redemptions on a vault you do not operate.
integer
The page size applied.
integer
The rows skipped.
boolean
true while rows beyond this page exist.
array
Every DEPOSIT and REDEEM on the vault, oldest first, as { txType, amount, timestamp }. Up to 5000 rows. It is not filtered by address and not capped by limit, so it covers the whole vault whoever asks. Use it to chart flows without paging the ledger.
Each read first brings the ledger up to date from the vault’s events, at most once a minute per vault. That sync stops at the last settled block: the finalized block, or five blocks behind the head on a chain that reports no finality. A transaction nobody confirmed therefore appears once its block is final. Report your own transactions to Confirm Transaction to see them sooner.

Error Codes