Skip to main content
Retrieves information about a Single Asset Vault, its owner, available assets, and details of its issued shares. Identify the vault either by vault_id or by owner and seq. This method will use 20 Compute Units.

Reference: Here

Parameters

  • vault_id (string, optional) The ledger entry ID of the Vault to be returned.
  • owner (string, optional) The account address of the Vault owner. Use together with seq.
  • seq (number, optional) The transaction sequence number that created the vault. Use together with owner.
  • ledger_hash (string, optional) The unique hash of the ledger version to use.
  • ledger_index (number or string, optional) The ledger index of the ledger to use, or a shortcut string such as validated.

Returns

  • vault (object) The vault description object: Account (the vault’s pseudo-account), Asset (currency and issuer, or mpt_issuance_id), AssetsAvailable, AssetsMaximum, AssetsTotal, Flags, index, LossUnrealized, Owner, Scale, ShareMPTID, WithdrawalPolicy, optional Data, LEVersion, VaultKind, RedemptionDate and SubscriptionDate, plus shares (the MPTokenIssuance entry for the vault’s shares).
  • ledger_hash, ledger_index or ledger_current_index, validated The ledger version used.
Over WebSocket, send {"id":1,"command":"vault_info","vault_id":"9E48171960CD9F62C3A7B6559315A510AE544C3F51E02947B5D4DAC8AA66C3BA","ledger_index":"validated"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.
The SingleAssetVault amendment is not yet enabled on XRPL mainnet (checked with feature on 28 September 2026), so there are no vaults to look up and a live call returns entryNotFound. The method is routed and billed as above and will return real data once the amendment activates.