Skip to main content
The DFNS Vaults API lets you create and operate vaults: managed, multichain custody primitives that hold assets under a single balance sheet with institutional accounting. A vault groups managed wallets across networks, segregates holdings into available, incoming, quarantined, and locked balances, and records every change in an immutable, append-only ledger. Incoming funds land quarantined until you release them, and funds move only through the vault’s transfer endpoints, never by signing the underlying wallets directly. Vaults are managed by organization users and service accounts, not delegated end users, and vault addresses are available on EVM networks today. For the concepts, see Vaults, wallets & keys; for the dashboard walkthrough, see Manage vaults. If you have feedback on the Vaults API, please reach out to our .

​
Webhooks

Vaults emit vault.created, vault.updated, vault.tags.modified, and vault.event.created events. Because a vault’s addresses are managed wallets, the same activity also emits the underlying wallet.* events — a deposit emits wallet.blockchainevent.detected and wallet.blockchain_event.transfer.included, and a vault transfer emits the full wallet.transfer.requested → broadcasted → confirmed sequence. If you subscribe to both, expect both, and key off the wallet or transfer id to avoid double-counting. See Webhook Events.

​
Vault object

Vault object.

​
id
string
required

Vault id.

Required string length: 1 - 64
Pattern: ^vlt-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$
Example:

"vlt-5vbsp-u62g1-ostmunqgds5o9tc2"

​
orgId
string
required
​
tags
string[]
required
​
dateCreated
string<date-time>
required
​
dateUpdated
string<date-time>
required
​
name
string
​
externalId
string
​
addresses
object[]

The vault's addresses.

Last modified on July 22, 2026