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 withseq.seq(number, optional) The transaction sequence number that created the vault. Use together withowner.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 asvalidated.
Returns
vault(object) The vault description object:Account(the vault’s pseudo-account),Asset(currencyandissuer, ormpt_issuance_id),AssetsAvailable,AssetsMaximum,AssetsTotal,Flags,index,LossUnrealized,Owner,Scale,ShareMPTID,WithdrawalPolicy, optionalData,LEVersion,VaultKind,RedemptionDateandSubscriptionDate, plusshares(the MPTokenIssuance entry for the vault’s shares).ledger_hash,ledger_indexorledger_current_index,validatedThe ledger version used.
{"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 withfeatureon 28 September 2026), so there are no vaults to look up and a live call returnsentryNotFound. The method is routed and billed as above and will return real data once the amendment activates.