Skip to main content
POST
Builds the two transactions a deposit needs: an ERC-20 approval for the vault to pull the settlement asset, then the deposit itself. Both come back as ordered steps for the depositor’s wallet to sign. The depositor receives vault shares at the current share price. Deposits are identity-gated. The vault admits only wallets its identity register verifies, and that register is fixed for the life of the vault. The operator’s register provider admits depositors.

Path Parameters

string
required
Vault ID.

Body Parameters

string
required
Amount to deposit as a decimal string, for example "1000". Denominated in the vault’s settlement asset and parsed at assetDecimals.
string
Wallet that will sign. When supplied, the API checks it against the vault’s identity register before offering a transaction and refuses with DEPOSITOR_NOT_VERIFIED if the deposit would revert on-chain. Omit it to skip the check. The contract enforces the gate either way.

Response Fields

object

When a deposit is refused on the vault’s own state

Two refusals are about the vault rather than about the depositor, and both exist to stop shares being issued against a number nobody can stand behind. Neither affects redemptions, which stay open throughout. A deposit is refused with VAULT_BOOK_INCOMPLETE when a market the vault funds is not answering. The vault cannot total its own book, so the share price it would issue at is a price computed from a partial book. The message names the market. It clears when that market answers again, or when the operator writes it off. A deposit is refused with VAULT_WIPED_OUT when shares are in issue against assets totalling zero. A deposit into that vault would be absorbed by the existing holders rather than buying a position. A vault whose value is gone cannot be recapitalized, and the operator has to run a new one.

Errors