# Blockdaemon Institutional Vault Documentation > Documentation for Blockdaemon Institutional Vault Append .md to any documentation page URL to get its markdown version. ## Guides - [Institutional Vault Overview](https://vault.docs.blockdaemon.com/docs/blockdaemon-wallet-overview.md): 👀 Find out what Institutional Vault is and how it works - [Security Model](https://vault.docs.blockdaemon.com/docs/security-model.md): Security model overview. - [MPC and TEE Security Architecture](https://vault.docs.blockdaemon.com/docs/mpc-tee-security-architecture.md): Defense-in-depth for MPC key shares using trusted execution environments, remote attestation, and hardware-bound encryption. - [Key Management Lifecycle](https://vault.docs.blockdaemon.com/docs/key-management-lifecycle.md) - [Cryptographic operations (MPC signing)](https://vault.docs.blockdaemon.com/docs/cryptographic-operations.md): How Institutional Vault uses MPC threshold signing for ECDSA and EdDSA (Ed25519). - [Transaction and approval flows](https://vault.docs.blockdaemon.com/docs/transaction-flows.md): How intents, approvals, policy evaluation, MPC signing, and broadcasting fit together. - [System Components](https://vault.docs.blockdaemon.com/docs/key-components.md) - [List of Terminologies](https://vault.docs.blockdaemon.com/docs/list-of-terminologies.md): 📚 List of terminologies used in the documentations. - [Getting Started](https://vault.docs.blockdaemon.com/docs/getting-started.md): How to get started with Institutional Vault. - [Onboarding the Wallet](https://vault.docs.blockdaemon.com/docs/onboarding-the-wallet.md): 👷 Setup your Institutional Vault Environment. - [Sign-In](https://vault.docs.blockdaemon.com/docs/sign-in.md): 🔑 Learn how to Sign-In to your Institutional Vault - [Register a User](https://vault.docs.blockdaemon.com/docs/register-user.md): 📝 Register a user to your Institutional Vault - [Delete a User](https://vault.docs.blockdaemon.com/docs/delete-a-user.md): 🪄Delete any account anytime you want - [Groups](https://vault.docs.blockdaemon.com/docs/groups.md): 🙋Manage your Institutional Vault User's group - [Reset a User](https://vault.docs.blockdaemon.com/docs/reset-a-user.md): 🔁Reset a user to register new Policy Engine - [Last Notifications](https://vault.docs.blockdaemon.com/docs/last-notifications.md): 🏫Learn the Last Notifications feature - [Automated Approver User](https://vault.docs.blockdaemon.com/docs/automated-approver-user.md): 👩‍💻 Find out how to delegate the approval process to the server - [Groups](https://vault.docs.blockdaemon.com/docs/groups-1.md): 🙋Manage your Institutional Vault User's group - [API User](https://vault.docs.blockdaemon.com/docs/api-user.md): Create an API User and API key for programmatic access - [Policy Management](https://vault.docs.blockdaemon.com/docs/policy-management.md) - [Transaction Restrictions](https://vault.docs.blockdaemon.com/docs/transaction-restrictions.md): Control who must approve on-chain operations - [Config Restrictions](https://vault.docs.blockdaemon.com/docs/config-restrictions.md): Require approvals for asset and chain changes, or block config initiation by group - [Policy Restrictions](https://vault.docs.blockdaemon.com/docs/policy-restrictions.md): Require approvals for governance changes - [Create an Account and Add Assets](https://vault.docs.blockdaemon.com/docs/create-account-and-add-assets.md): 📦 Create accounts and enable blockchain assets to generate wallet addresses. - [Transfer Funds](https://vault.docs.blockdaemon.com/docs/transfer-funds.md): 📤Find out how to transfer funds to another accounts - [Receive Funds](https://vault.docs.blockdaemon.com/docs/receive-funds.md): 🤑 Learn how to receive funds within your Institutional Vault - [Set Boundaries for Accepted Exchange Rates](https://vault.docs.blockdaemon.com/docs/️set-boundaries-for-accepted-exchange-rates.md): ✍️ Set a range of acceptable exchange rates or a set rate - [Stake Assets](https://vault.docs.blockdaemon.com/docs/stake-assets.md): 🪙Find out how to stake assets - [Unstake Assets](https://vault.docs.blockdaemon.com/docs/unstake-assets.md): 🪙Find out how to unstake assets - [Transaction History](https://vault.docs.blockdaemon.com/docs/transaction-history.md): 🧾See your wallet's transaction history - [Add ERC-20 Assets](https://vault.docs.blockdaemon.com/docs/add-erc-20-assets.md): 🔝Add ERC-20 tokens - [Export Audit Logs](https://vault.docs.blockdaemon.com/docs/export-audit-logs.md): Export Institutional Vault audit logs for compliance and forensics - [Offline & Online Accounts Pairing](https://vault.docs.blockdaemon.com/docs/how-to-pair-offline-online-accounts-in-blockdaemon-institutional-wallet.md): 🤝 Pair your hot and cold wallet! - [Create, Sign and Broadcast Transactions](https://vault.docs.blockdaemon.com/docs/how-to-create-sign-and-broadcast-the-cold-institutional-wallet-transactions.md): 🌨️ Find out how to do a transaction with Cold Wallet. - [Stake Assets](https://vault.docs.blockdaemon.com/docs/1-1.md): 🪙 Find out how to stake assets with Cold Wallet. - [ERS Backup Download](https://vault.docs.blockdaemon.com/docs/cold-wallet-ers-backup-download.md) - [System Backup](https://vault.docs.blockdaemon.com/docs/cold-wallet-system-backup.md) - [Back Up Master Key](https://vault.docs.blockdaemon.com/docs/backup-master-key.md): 🔐 Back up your Institutional Vault master key - [Emergency Recovery](https://vault.docs.blockdaemon.com/docs/emergency-recovery.md): ⚠️ Discover how to retrieve Master Key in an emergency - [Create ERS Encryption Key](https://vault.docs.blockdaemon.com/docs/create-ers-key.md): Generate the ERS RSA key pair before wallet install - [Tokenization](https://vault.docs.blockdaemon.com/docs/tokenization.md): Deploy, mint, and burn ERC-20 tokens using the Institutional Vault Core Wallet Platform API on a sandbox environment. - [WalletConnect Usage](https://vault.docs.blockdaemon.com/docs/walletconnect-usage.md) - [Transaction Risk Assessment](https://vault.docs.blockdaemon.com/docs/transaction-risk-assessment.md) - [Frequently Asked Questions](https://vault.docs.blockdaemon.com/docs/frequently-asked-questions.md): ⁉️ Find Answers to your questions here! - [Sandbox Enrollment & Onboarding](https://vault.docs.blockdaemon.com/docs/blockdaemon-wallet-sandbox-enrollment-process.md): Request a hosted test environment and onboard your technical team to the Institutional Vault sandbox. - [Cloud-agnostic Install Guide](https://vault.docs.blockdaemon.com/docs/generic-install-process.md) - [AWS ECS Deployment Process](https://vault.docs.blockdaemon.com/docs/aws-ecs-deployment-process.md): 💡Find out how to set up a Production Institutional Vault on your own. - [Deployment Specifications](https://vault.docs.blockdaemon.com/docs/wallet-aws-sizing-and-quotas-page.md): 📝 Understand the Wallet AWS networking, sizing and quotas. - [AWS Installation Troubleshooting](https://vault.docs.blockdaemon.com/docs/aws-installation-troubleshooting.md) - [Confidential Computing - Remote Attestation and Secret Injection](https://vault.docs.blockdaemon.com/docs/confidential-computing-remote-attestation-and-secret-injection.md) - [How to export logs for troubleshooting](https://vault.docs.blockdaemon.com/docs/how-to-export-logs-for-troubleshooting-prod.md) - [Installation Troubleshooting](https://vault.docs.blockdaemon.com/docs/installation-troubleshooting.md) - [Azure Deployment Process](https://vault.docs.blockdaemon.com/docs/azure-deployment-process.md) - [Azure Installation Troubleshooting](https://vault.docs.blockdaemon.com/docs/azure-installation-troubleshooting.md): How to troubleshoot common issues for Azure Installation. - [How to export logs for troubleshooting](https://vault.docs.blockdaemon.com/docs/how-to-export-logs-for-troubleshooting.md) - [Azure Deployment Specifications](https://vault.docs.blockdaemon.com/docs/wallet-azure-sizing-and-quotas-page.md): 📝 Understand the Wallet Azure networking, sizing and quotas. - [OIDC IdP Configuration](https://vault.docs.blockdaemon.com/docs/oidc-idp-configuration.md): Configure an OIDC-compatible IdP for Vault UI and ApproverApp - [Auth0 IdP Configuration](https://vault.docs.blockdaemon.com/docs/configuring-auth0.md): ✔️ Configuring Auth0 for wallet and approver application! - [Entra IdP Configuration](https://vault.docs.blockdaemon.com/docs/configuring-entra.md): ✔️ Configuring Microsoft Entra ID for your wallet and approver application! - [Okta IdP Configuration](https://vault.docs.blockdaemon.com/docs/configuring-okta.md): ✔️ Configuring Okta for your wallet and approver application! - [customer-config.yml Reference](https://vault.docs.blockdaemon.com/docs/customer-config-reference.md): Field-by-field reference for the customer-owned deployment configuration file. - [Helm Deployment](https://vault.docs.blockdaemon.com/docs/helm-deployment.md): Deploy the Institutional Vault on your own Kubernetes cluster using the Blockdaemon Helm chart. - [Cluster Prerequisites](https://vault.docs.blockdaemon.com/docs/cluster-prerequisites.md): Install the shared cluster-scoped operators and cert-manager issuers required by all Institutional Vault instances. - [AWS EKS Installation](https://vault.docs.blockdaemon.com/docs/aws-eks.md): Install the Institutional Vault on Amazon EKS using IRSA and AWS Secrets Manager. - [Azure AKS Installation](https://vault.docs.blockdaemon.com/docs/azure-aks.md): Install the Institutional Vault on Azure Kubernetes Service using workload identity and Azure Key Vault. - [GCP GKE Installation](https://vault.docs.blockdaemon.com/docs/gcp-gke.md): Install the Institutional Vault on Google Kubernetes Engine using Workload Identity and GCP Secret Manager. - [Upgrading](https://vault.docs.blockdaemon.com/docs/upgrading.md): Upgrade the Institutional Vault to a new version using helm upgrade, with automatic DB migrations and safe rollback. - [Cold Wallet Deployment](https://vault.docs.blockdaemon.com/docs/cold-wallet-deployment.md) - [Metrics and Health](https://vault.docs.blockdaemon.com/docs/wallet-metrics-and-health-page.md): Understand wallet metrics, Vault operations metrics, system health, and application logging. - [System Backup and Restore Process](https://vault.docs.blockdaemon.com/docs/wallet-state-backup-and-restore-process.md) - [Wallet Upgrade Processes](https://vault.docs.blockdaemon.com/docs/how-to-perform-wallet-upgrade.md) - [AWS Wallet Upgrade](https://vault.docs.blockdaemon.com/docs/aws-wallet-upgrade.md) - [Azure Wallet Upgrade](https://vault.docs.blockdaemon.com/docs/azure-wallet-upgrade.md) - [Troubleshooting Guide](https://vault.docs.blockdaemon.com/docs/troubleshooting-guide.md): MPA error codes, HTTP statuses, and resolution steps for Institutional Vault. - [Rotate Encryptor Master Password](https://vault.docs.blockdaemon.com/docs/rotate-encryptor-master-password.md): Rotate Policy Node Encryptor Master Passwords with a safe dual-config transition. - [MCP](https://vault.docs.blockdaemon.com/docs/mcp.md) ## API Reference - [Quick Start - Institutional Vault APIs](https://vault.docs.blockdaemon.com/reference/quick-start-blockdaemon-wallet.md): 👋 Welcome! Get started with the Institutional Vault API. - [Generate Client SDKs](https://vault.docs.blockdaemon.com/reference/generate-client-sdks.md) - [Get a List of Assets](https://vault.docs.blockdaemon.com/reference/getallassetssummary.md): Retrieve a summary of all assets including the asset type, total balance and amount in USD. - [Add an Additional Address to an Asset](https://vault.docs.blockdaemon.com/reference/addaddress.md): Adds an address to the asset uniquely specified by VaultId and Asset. The name specified for the address must be unique. Be aware that this endpoint will not work for ethereum assets, since it is only possible to have a single address for such assets. - [Return a list of supported assets](https://vault.docs.blockdaemon.com/reference/getsupportedassets.md): Returns all assets supported by this wallet, including native L1 assets and imported tokens (ERC-20, SPL, Canton CIP56). - [Add Support for an Additional ERC20, SPL, or Canton CIP56 Token Asset](https://vault.docs.blockdaemon.com/reference/addblockchainsupportedasset.md): Adds support for a new token asset. Use `Blockchain` to select the variant: `ethereum`, `polygon`, `base`, or `besu` with `ContractAddress` for ERC-20; `solana` with `ContractAddress` for SPL; `canton` with `InstrumentID` and `RegistrarPartyID` for Canton CIP56 tokens. - [Return a list of supported chains](https://vault.docs.blockdaemon.com/reference/getsupportedchains.md): Return a list of supported chains - [Get a List of Assets and Their Exchange Rate](https://vault.docs.blockdaemon.com/reference/getexchangerates.md): Retrieves a list of all assets and their respective exchange rate. The list is in descending order based on the USDRate. If the asset does not have an exchange rate, USDRate will be set to null. If the asset has a pending exchange rate update the PendingUSDRate field will be set, if not it will be null - [Set Exchange Rate of an Asset](https://vault.docs.blockdaemon.com/reference/setexchangerate.md): Sets the exchange rate of asset specified by asset.The Rate should be set in USD. You can either set a fixed rate or set a range the rate is allowed to move in. If the range is set, the rate will be set by querying 3'rd parties and used so long they are in the given range. The exchange rate can only be set on assets with "Status" = "Success" - [Get a Single Asset](https://vault.docs.blockdaemon.com/reference/getassetdetails.md): Retrieve details of a single asset including the vaults, under which the asset is present. If the exclude_empty parameter is also set, only Assets with currency will be returned. - [Get a Validators for a Single Asset](https://vault.docs.blockdaemon.com/reference/getsummaryofassetsvalidators.md): Retrieve details of all validators for an asset. - [Register Token](https://vault.docs.blockdaemon.com/reference/cwpstartregistertoken.md): Start an async Register Token operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Register Custom Chain](https://vault.docs.blockdaemon.com/reference/cwpstartregistercustomchain.md): Start an async Register Custom Chain operation. Registers a custom chain (CAIP-2) and its native asset (CAIP-19). The chain ID is derived from the native asset type. The operation is idempotent; registering an already-known chain updates it. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Unregister Token](https://vault.docs.blockdaemon.com/reference/cwpstartunregistertoken.md): Start an async Unregister Token operation. Removes a token previously registered with `registerToken`. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Unregister Chain](https://vault.docs.blockdaemon.com/reference/cwpstartunregisterchain.md): Start an async Unregister Chain operation. Removes a chain previously registered with `registerCustomChain`. Fails if any non-native tokens are still registered on the chain; unregister them first. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [List registered chains](https://vault.docs.blockdaemon.com/reference/cwplistchains.md): Returns all chains registered for the tenant (name, CAIP-2, testnet flag). - [Register a known chain](https://vault.docs.blockdaemon.com/reference/cwpregisterknownchain.md): Register a chain from the built-in chain registry. All chain metadata (name, native asset, coin type, decimals, etc.) is resolved from the CAIP-2 identifier. The call is idempotent: succeeds if the chain is already registered with identical data, but fails if existing data conflicts. - [List registered tokens](https://vault.docs.blockdaemon.com/reference/cwplisttokens.md): Returns all tokens registered for the tenant (symbol, decimals, CAIP-2, CAIP-19, chain name, testnet). - [Delete Token (deprecated)](https://vault.docs.blockdaemon.com/reference/cwpstartdeletetoken.md): **Deprecated:** Use [`POST /operations/start/unregisterToken`](#/paths/~1operations~1start~1unregisterToken/post) with required `CAIP19` instead. This route accepts legacy symbol-based input (`Symbol`, optional `ChainName`/`TestNetwork`); the server resolves those fields to CAIP-19 at start. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Associate to SPL Token](https://vault.docs.blockdaemon.com/reference/cwpstartassociatetospltoken.md): Start an async Associate to SPL Token operation. Creates an associated token account for the given SPL token. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Associate Nonce Account](https://vault.docs.blockdaemon.com/reference/cwpstartassociatenonceaccount.md): Start an async Associate Nonce Account operation. Creates a Solana nonce account for durable transactions. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Activate Stellar Address](https://vault.docs.blockdaemon.com/reference/cwpstartactivatestellaraddress.md): Start an async Activate Stellar Address operation. Funds and activates a Stellar address with the minimum XLM balance. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Search asset infos](https://vault.docs.blockdaemon.com/reference/cwpsearchassetinfos.md): Returns asset information for all tokens matching the filter. All filter fields are optional. An empty filter returns all registered assets. Filter by CAIP-2 chain ID, chain name, CAIP-19 asset type, symbol, or test network. - [Get token metadata](https://vault.docs.blockdaemon.com/reference/cwpgettokenmetadata.md): Returns the symbol and decimals for an asset (CAIP-19), looked up directly from the chain. Symbol and decimals are omitted if they could not be determined for this asset. - [Transfer Funds to an Internal Vault or External Address](https://vault.docs.blockdaemon.com/reference/screen.md): Screen a potential transaction against OFAC compliance. - [Get Compliance Settings](https://vault.docs.blockdaemon.com/reference/getcompliancesettings.md): return compliance settings - [Edit Compliance Settings](https://vault.docs.blockdaemon.com/reference/editcompliancesettings.md): toggle compliance settings - [View the Config](https://vault.docs.blockdaemon.com/reference/viewconfig.md): Gets The Configuration Of The Wallet - [Get Tenant Configuration](https://vault.docs.blockdaemon.com/reference/viewtenantconfig.md): Gets The Configuration Of The Tenant - [Get Runtime Resource Identifier](https://vault.docs.blockdaemon.com/reference/getruntimeresourceidentifier.md): Returns the Runtime Resource Identifier - [Get Event State](https://vault.docs.blockdaemon.com/reference/geteventstate.md): Returns the event state of the wallet given the runtime resource identifier stored internally. - [Get QR Redirect Link](https://vault.docs.blockdaemon.com/reference/qrredirect.md): Retrieves approver app download link depending on `User-Agent` header - [List the Master Keys](https://vault.docs.blockdaemon.com/reference/listmasterkeys.md): list master keys in hot wallet - [Create Batch](https://vault.docs.blockdaemon.com/reference/cwpstartcreatebatch.md): Start an async Create Batch operation. Opens a signing batch for a master key; transactions are queued until the batch is finished or deleted. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Finish Current Batch](https://vault.docs.blockdaemon.com/reference/cwpstartfinishcurrentbatch.md): Start an async Finish Current Batch operation. Closes the open batch and submits partial signatures for all queued transactions. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Delete Current Batch](https://vault.docs.blockdaemon.com/reference/cwpstartdeletecurrentbatch.md): Start an async Delete Current Batch operation. Discards the open batch without signing. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Logout the Current User](https://vault.docs.blockdaemon.com/reference/logoutendpoint.md): Logs the user out - [Get a User Details](https://vault.docs.blockdaemon.com/reference/getuserinfo.md): Retrieves the role and status of user whose ID is in the token. - [Register User](https://vault.docs.blockdaemon.com/reference/cwpstartregisteruser.md): Start an async Register User operation. Adds a user that can participate in approval workflows. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Set User Public Key](https://vault.docs.blockdaemon.com/reference/cwpstartsetuserpublickey.md): Start an async Set User Public Key operation. Associates a public key with a registered user. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Delete User](https://vault.docs.blockdaemon.com/reference/cwpstartdeleteuser.md): Start an async Delete User operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Reset User](https://vault.docs.blockdaemon.com/reference/cwpstartresetuser.md): Start an async Reset User operation. Resets a user's state (e.g. after device loss). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Get User](https://vault.docs.blockdaemon.com/reference/cwpgetuserbyid.md): Get a user by ID. - [List Users](https://vault.docs.blockdaemon.com/reference/cwplistusers.md): List all registered users. - [Get All Group Members](https://vault.docs.blockdaemon.com/reference/cwpgetallgroupmembers.md): Returns all groups and their member user IDs. - [List Group Members](https://vault.docs.blockdaemon.com/reference/cwplistgroupmembers.md): List all members of a named group. - [List API Keys](https://vault.docs.blockdaemon.com/reference/cwplistapikeys.md): Returns all API keys (user ID and label only). - [Create API Key](https://vault.docs.blockdaemon.com/reference/cwpcreateapikey.md): Creates a new API key for the given user. The key is returned only once in this response — store it securely. - [Delete API Key](https://vault.docs.blockdaemon.com/reference/cwpdeleteapikey.md): Deletes the API key identified by the given user ID and label. Succeeds without error if the key does not exist (idempotent). - [Retrieve the Backup Master Key](https://vault.docs.blockdaemon.com/reference/backup.md): Synchronously retrieves a backup of the master key used in the MPA. - [Get All Vaults](https://vault.docs.blockdaemon.com/reference/getvaults.md): Get all vaults. - [Get Assets Not in Vault](https://vault.docs.blockdaemon.com/reference/getassetsnotinvault.md): Retrieves a list of all the assets that are not yet added to the vault matching the id - [Get a Vault](https://vault.docs.blockdaemon.com/reference/getvault.md): Retrieves a single vault by UUID in request URL. - [Add an Asset to a Vault](https://vault.docs.blockdaemon.com/reference/addasset.md): Adds an asset of type 'Asset' to the vault specified by 'VaultId'. A vault can only contain a single asset of each asset type. - [Add Solana Asset to Cold Vault](https://vault.docs.blockdaemon.com/reference/addsolanacoldasset.md): Initiates the creation of a Solana Nonce account for a cold (offline) account, enabling offline transaction signing. This is required before a cold vault can send Solana transactions. The operation creates a durable nonce account on Solana which replaces the recent blockhash requirement, allowing transactions to be signed offline and submitted at any later time. A hot (online) account with SOL balance is required to pay for the nonce account creation (rent-exempt balance + fees). - [Get the Address of the Asset](https://vault.docs.blockdaemon.com/reference/getaddressofasset.md): Retrieve the addresses of the asset identified by its CAIP-19 identifier under the vault specified by the "id" parameter. - [Backup Master Key](https://vault.docs.blockdaemon.com/reference/cwpstartbackupmasterkey.md): Start an async Backup Master Key operation. Returns encrypted key shares for offline storage. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create Master Key](https://vault.docs.blockdaemon.com/reference/cwpstartcreatemasterkey.md): Start an async Create Master Key operation. Generates a new MPC master key via distributed key generation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create Account](https://vault.docs.blockdaemon.com/reference/cwpstartcreateaccount.md): Start an async Create Account operation. Creates a named account under an existing master key. When starting via this CWP endpoint, include `InitiatorID` set to a registered Vault user email so the Vault gateway can create the matching account record when it receives operation status updates. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Attach Master Key](https://vault.docs.blockdaemon.com/reference/cwpstartattachmasterkey.md): Start an async Attach Master Key operation. Attaches an externally generated master key using pairing messages. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Set ERS Public Key](https://vault.docs.blockdaemon.com/reference/cwpstartseterspublickey.md): Start an async Set ERS Public Key operation. Sets the RSA public key (PKIX DER) used for encrypted recovery shares. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [List accounts](https://vault.docs.blockdaemon.com/reference/cwplistaccounts.md): Returns all accounts registered for the tenant, across all master keys. - [List master keys](https://vault.docs.blockdaemon.com/reference/cwplistmasterkeys.md): Returns all master keys registered for the tenant. - [Get the Notifications](https://vault.docs.blockdaemon.com/reference/getnotifications.md): Retrieves notifications from the last 7 days. - [Set the Last Seen Time](https://vault.docs.blockdaemon.com/reference/setlastseen.md): Sets the time when the calling user has last seen notifications (aka when the bell icon is pressed) - [Subscribe to Updates](https://vault.docs.blockdaemon.com/reference/subscribetoupdates.md): NB: This endpoint is described as a normal REST API call, but it is actually a websocket connection, so access it like that. The models can be used still since they will be correct - [Get Operation Status](https://vault.docs.blockdaemon.com/reference/getoperationstatus.md): Retrieves the current status of the given MPC operation, by ID - [Cancel operation](https://vault.docs.blockdaemon.com/reference/canceloperation.md): Cancel operation by id - [Search operations](https://vault.docs.blockdaemon.com/reference/cwpsearchoperations.md): **Deprecated:** Prefer [`POST /operations/searchInfos`](#/paths/~1operations~1searchInfos/post) when you need a stable sort or pagination without unmarshalling full intents. Returns operations' intents matching the filter. If `Statuses` is omitted or empty, only operations that are not in a final state (`Succeeded` or `Failed`) are included. There is **no limit** field on the filter; this endpoint may return unbounded payloads. Matches are returned in **arbitrary order** (not ordered by creation time). The 200 response body is a **`ListOperationsResult`**: `Intents` is a JSON array of **stored intent objects** (standard `application/json` encoding of each intent struct). Each element matches one variant of **`IntentItem`** when the operation type is still startable over HTTP; use the object's **`OperationType`** field to select the variant. Older operation types that can no longer be started (for example `transfer`, `add ERC20 asset`) may still appear in responses but are omitted from the `IntentItem` union. This is not a base64 blob, `json.RawMessage`, or double-encoded JSON string layer. Returned intents include common metadata when present: `OperationType`, optional `OperationID` and `InitiatorID`, and server fields such as `Timestamp` and `InitiatorName` (see each variant under `IntentItem`). - [Search operation summaries](https://vault.docs.blockdaemon.com/reference/cwpsearchoperationinfos.md): Returns lightweight metadata. for operations matching `Filter`. Results are ordered by `CreatedTime` descending, with `OperationID` as a tiebreaker (also descending). If `Statuses` is omitted or empty, only operations that are not in a final state (`Succeeded` or `Failed`) are included. Use `Pagination.Size` to cap how many rows are returned per call. When more rows remain, `PaginationToken` is non-empty — pass its value as `Pagination.Token` on the next request. If `Pagination.Size` is zero or omitted, all matching rows are returned in one response and `PaginationToken` is empty. - [Get operation status](https://vault.docs.blockdaemon.com/reference/cwpgetoperationstatus.md) - [Get operation approval status](https://vault.docs.blockdaemon.com/reference/cwpgetoperationapprovalstatus.md) - [Get operation intent](https://vault.docs.blockdaemon.com/reference/cwpgetoperationintent.md): Returns the stored intent JSON for the operation. Startable operation types match one variant of [`IntentItem`](#/components/schemas/IntentItem), including `OperationType` and server-populated fields such as `Timestamp` and `InitiatorName` when present. Older operation types that can no longer be started over HTTP may still be returned but are omitted from the `IntentItem` union. - [Cancel an operation](https://vault.docs.blockdaemon.com/reference/cwpcanceloperation.md): Sets the operation state to Failed. Returns an error if the operation is already in a final state. - [Cancel an operation](https://vault.docs.blockdaemon.com/reference/cwpcanceloperationdelete.md): Sets the operation state to Failed. Returns an error if the operation is already in a final state. - [Get All the Staking Assets](https://vault.docs.blockdaemon.com/reference/getallstakingassets.md): Retrieve a summary of staking assets - [Stake Funds](https://vault.docs.blockdaemon.com/reference/stake.md): Stake funds from one vault (of a certain type of asset) and enable withdrawal on the given address - [Withdraw the Staked Assets](https://vault.docs.blockdaemon.com/reference/stakingwithdrawal.md): Withdraw asset from validators - [Get the Vault Validators](https://vault.docs.blockdaemon.com/reference/getvaultvalidators.md): Retrieves a list of all validators for a single vault by UUID in request URL. - [Stake](https://vault.docs.blockdaemon.com/reference/cwpstartstake.md): Start an async Stake operation. Stakes assets to a validator on the specified chain. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Unstake](https://vault.docs.blockdaemon.com/reference/cwpstartunstake.md): Start an async Unstake operation. Unstakes from the specified validators. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [List Tenants](https://vault.docs.blockdaemon.com/reference/listtenants.md): Retrieves a list of all tenants - [Setup Default Tenant](https://vault.docs.blockdaemon.com/reference/setupdefaulttenant.md): Populates the default tenant with initial state (master keys, policies, blockchain networks). Can only be called once on an empty tenant. - [Get All Transactions](https://vault.docs.blockdaemon.com/reference/showtransactions.md): Retrieves all transactions for the given page and page size. - [Consolidate Funds](https://vault.docs.blockdaemon.com/reference/consolidatefunds.md): Consolidate funds - [Export All Transactions](https://vault.docs.blockdaemon.com/reference/exporttransactions.md): Get all Export all transactions as csv - [Get Transaction Filter Details](https://vault.docs.blockdaemon.com/reference/getfilterdetails.md): Details needed to fill out filter. The details includes a list of all users, assets and vaults in the system - [Fund Multiple Sub-Addresses](https://vault.docs.blockdaemon.com/reference/fundsubaddresses.md): Fund multiple sub-addresses - [Transfer the Funds to a Vault or and Address](https://vault.docs.blockdaemon.com/reference/transferfunds.md): Transfers funds from one vault (of a certain type of asset) to an internal vault or an external address. When making an Internal request destination must be the vaultId for the destination vault. When making an External request destination must be the address. - [Get the Transfer Details](https://vault.docs.blockdaemon.com/reference/gettransferdetails.md): Return asset details including current balance, exchange rate, fee. - [Get the Transactions Vault](https://vault.docs.blockdaemon.com/reference/showtransactionsforvault.md): Retrieves all transactions for the given page, page size and vaultId. - [Get a Single Transaction](https://vault.docs.blockdaemon.com/reference/gettransaction.md): Retrieves a single transaction with the provided TransactionId - [Make Transaction](https://vault.docs.blockdaemon.com/reference/cwpstartmaketransaction.md): Start an async Make Transaction operation. With structured `Destination` (and optional `EVM` / chain-specific fields), creates, signs, and broadcasts the transaction when complete. With `RawTransaction` (and optional `TxHash` for Canton prepared submission), MPC signing only—the operation does **not** broadcast; the response includes `SignedTransaction` and the integrator must submit the signed bytes to the network. Requires `Source` as `AddressSpec` and `CAIP19`. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Generic Signing](https://vault.docs.blockdaemon.com/reference/cwpstartgenericsigning.md): Start an async Generic Signing operation. Signs arbitrary data (e.g. personal_sign, typed data). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Sign Raw Transaction (deprecated)](https://vault.docs.blockdaemon.com/reference/cwpstartsignrawtransaction.md): **Deprecated:** Use [`POST /operations/start/makeTransaction`](#/paths/~1operations~1start~1makeTransaction/post) with `Source` (`AddressSpec`), required `CAIP19`, and `RawTransaction` instead (same sign-only behavior: MPC signature only, no broadcast). This route uses a legacy flat payload (`MasterKeyName`, account-name `Source`, `Asset`). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Sponsor](https://vault.docs.blockdaemon.com/reference/cwpstartsponsor.md): Start an async Sponsor operation. Sponsors contract calls via EIP-7702 authorization. Requires `Data` and optionally `EIP7702Authorizations` in the EVM spec. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Consolidate Funds](https://vault.docs.blockdaemon.com/reference/cwpstartconsolidatefunds.md): Start an async Consolidate Funds operation. Moves funds from a sub-address back to the main address. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Fund Subaddresses](https://vault.docs.blockdaemon.com/reference/cwpstartfundsubaddresses.md): Start an async Fund Subaddresses operation. Distributes funds from the main address to multiple sub-addresses. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Generate Consolidation Data](https://vault.docs.blockdaemon.com/reference/cwpstartgenerateconsolidationdata.md): Start an async Generate Consolidation Data operation. Computes call data and EIP-7702 authorizations needed for a subsequent consolidation transaction. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create Allocation](https://vault.docs.blockdaemon.com/reference/cwpstartcreateallocation.md): Start an async Create Allocation operation. Creates a Canton allocation for a settlement workflow with executor, deadlines, and destination amounts. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Canton Enrollment](https://vault.docs.blockdaemon.com/reference/cwpstartcantonenrollment.md): Start an async Canton Enrollment operation. Enrolls an external party on the Canton ledger. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Canton Preapproval](https://vault.docs.blockdaemon.com/reference/cwpstartcantonpreapproval.md): Start an async Canton Preapproval operation. Creates a transfer preapproval for a Canton party. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [End Investor Onboarding Offer (Canton)](https://vault.docs.blockdaemon.com/reference/cwpstartcallchoiceonendinvestoronboardingoffer.md): Start an async operation to exercise a choice on a Canton end-investor-onboarding offer contract (operation type `call choice on end investor onboarding offer`). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Health Check](https://vault.docs.blockdaemon.com/reference/health-1.md): Shows Whether API Is Healthy - [Readiness Check](https://vault.docs.blockdaemon.com/reference/ready.md): Shows whether API is ready - [Get address (deprecated)](https://vault.docs.blockdaemon.com/reference/cwpgetaddress.md): Deprecated: Use `POST /addresses/get` instead. Gets an address for the native asset in the specified master key and account. For a given (masterKey, account, symbol, testnet), a previously unused index can only take a value one greater than the maximal previously used index (zero if no previous calls). - [Get address](https://vault.docs.blockdaemon.com/reference/cwpgetaddresscaip2.md): Gets an address for the native asset of the chain identified by CAIP-2. For a given (masterKey, caip2, account), a previously unused index can only take a value one greater than the maximal previously used index (zero if no previous calls). - [Resolve address](https://vault.docs.blockdaemon.com/reference/cwpresolveaddress.md): Resolves a blockchain address to the master key, account, and address index that own it. - [Get Solana nonce account count](https://vault.docs.blockdaemon.com/reference/cwpgetsolanaaccountinfo.md): Returns the number of nonce accounts associated with the authority account on the given Solana chain. Send `CAIP2` and `Address` ([`AddressSpec`](#/components/schemas/AddressSpec)). Use either a literal `Address`, or `MasterKeyName`, `AccountName`, and `AddressIndex` together. - [Update Config Restriction](https://vault.docs.blockdaemon.com/reference/cwpstartupdateconfigrestriction.md): Start an async Update Config Restriction operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Update Policy Restriction](https://vault.docs.blockdaemon.com/reference/cwpstartupdatepolicyrestriction.md): Start an async Update Policy Restriction operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Update Transaction Restriction](https://vault.docs.blockdaemon.com/reference/cwpstartupdatetransactionrestriction.md): Start an async Update Transaction Restriction operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Update Rates](https://vault.docs.blockdaemon.com/reference/cwpstartupdaterates.md): Start an async Update Rates operation. Sets USD spot rates or min/max bounds for assets used in policy evaluation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Get config restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetconfigrestrictions.md): Returns the tenant's config restrictions. These apply to config-related operations (e.g. adding tokens, registering blockchain networks). When a restriction applies, the specified approvers must approve before the operation can execute. - [Get policy restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetpolicyrestrictions.md): Returns the tenant's policy restrictions. These apply to policy-related operations (e.g. updating policy set, group, or restriction rules). When a restriction applies, the specified approvers must approve before the operation can execute. - [Get transaction restrictions](https://vault.docs.blockdaemon.com/reference/cwpgettransactionrestrictions.md): Returns the tenant's transaction restrictions. These apply to transaction operations (e.g. transfers). Each restriction has a filter with criteria (amount, fee, symbol, source, destination, etc.). A restriction applies when its filter matches — i.e. when all criteria are satisfied. When a restriction applies, the specified approvers must approve before the operation can execute. - [Get operation types for config restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetoperationtypesforconfig.md): Returns the operation types that are covered by config restrictions. Use these when configuring restrictions via `GET /restrictions/config`. - [Get operation types for policy restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetoperationtypesforpolicy.md): Returns the operation types that are covered by policy restrictions. Use these when configuring restrictions via `GET /restrictions/policy`. - [Get operation types for transaction restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetoperationtypesfortransaction.md): Returns the operation types that are covered by transaction restrictions. Use these when configuring restrictions via `GET /restrictions/transaction`. - [Names used when filtering transactions by function](https://vault.docs.blockdaemon.com/reference/cwpgetrestrictiontransactionfunctionnames.md): Returns the names you can use when a transaction restriction should apply only to certain kinds of on-chain actions. Call this endpoint whenever you need the current list; it may change as the product evolves. - [Update Group](https://vault.docs.blockdaemon.com/reference/cwpstartupdategroup.md): Start an async Update Group operation. Adds or removes users from a named group. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Rename Group](https://vault.docs.blockdaemon.com/reference/cwpstartrenamegroup.md): Start an async Rename Group operation. Renames a group and updates all restriction references to the old group name. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create a group](https://vault.docs.blockdaemon.com/reference/cwpcreategroup.md): Creates a new group with the given name. If a group with that name already exists, the operation succeeds without error (idempotent). - [Subscribe to events](https://vault.docs.blockdaemon.com/reference/cwpsubscribetoevents.md): Upgrades the connection to WebSocket. The server pushes `ClientEvent` messages; the client does not send data messages. Event types: - `operation_status_update` — an operation changed status. Payload: `OperationStatusUpdatePayload`. - `approver_onboarded` — an approver completed onboarding. Payload: `ApproverOnboardedPayload`. Delivery order of events is not guaranteed. To get the current state, query the server. - [Get USD prices](https://vault.docs.blockdaemon.com/reference/cwpgetusdprices.md): Returns the USD price for each of the given assets (CAIP-19). - [Set Up Public Key](https://vault.docs.blockdaemon.com/reference/cwpsetuppublickey.md): Registers the approver's ECDSA public key for the authenticated user, enabling them to sign and verify operation approvals. - [List Pending Approvals](https://vault.docs.blockdaemon.com/reference/cwplistapprovals.md): Returns the operations currently pending approval or confirmation for the given user. - [Approve Operation](https://vault.docs.blockdaemon.com/reference/cwpapproveoperation.md): Registers an approval of the specified operation by the given user. `IntentSignature` must be a signature of the operation's intent made with the user's private key. - [Reject Operation](https://vault.docs.blockdaemon.com/reference/cwprejectoperation.md): Registers a rejection of the specified operation by the given user. - [Register Device](https://vault.docs.blockdaemon.com/reference/cwpregisterdevice.md): Registers an Expo push notification device token for the user. Replaces any previously registered token for the same user. - [Unregister Device](https://vault.docs.blockdaemon.com/reference/cwpunregisterdevice.md): Removes the registered Expo push notification device token for the user. A no-op if no token is registered. - [Get on-chain balance](https://vault.docs.blockdaemon.com/reference/cwpgetonchainbalance.md): Returns the confirmed on-chain balance for the given master key, account, and asset (CAIP-19), aggregated across all derived addresses. The balance is a major-unit decimal string (e.g. `"0.25"`). - [Get spendable balance](https://vault.docs.blockdaemon.com/reference/cwpgetspendablebalance.md): Returns the spendable balance for the given master key, account, and asset (CAIP-19). - [Get on-chain token balances](https://vault.docs.blockdaemon.com/reference/cwpgetonchaintokenbalances.md): Returns the confirmed on-chain balance for all registered tokens, summed across all accounts. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Get spendable token balances](https://vault.docs.blockdaemon.com/reference/cwpgetspendabletokenbalances.md): Returns the spendable balance for all registered tokens, summed across all accounts. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Get on-chain token balances for account](https://vault.docs.blockdaemon.com/reference/cwpgetonchaintokenbalancesforaccount.md): Returns the confirmed on-chain balance for each token the account has addresses for. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Get spendable token balances for account](https://vault.docs.blockdaemon.com/reference/cwpgetspendabletokenbalancesforaccount.md): Returns the spendable balance for each token the account has addresses for. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Pair with a WalletConnect dApp](https://vault.docs.blockdaemon.com/reference/cwpwalletconnectwalletconnectpair.md): Initiates a WalletConnect pairing using the URI from a dApp's QR code or deep link. The wallet will automatically negotiate supported chains and accounts with the dApp. - [Disconnect a WalletConnect session](https://vault.docs.blockdaemon.com/reference/cwpwalletconnectwalletconnectdisconnect.md): Disconnects an active WalletConnect session or cancels a pending pairing. The session must belong to the calling tenant. - [List active WalletConnect sessions](https://vault.docs.blockdaemon.com/reference/cwpwalletconnectwalletconnectlistsessions.md): Returns active WalletConnect sessions for the calling tenant. Results can be filtered by master key, account, and initiator user ID. The accountName filter also requires masterKeyName to be specified. - [Download audit logs](https://vault.docs.blockdaemon.com/reference/listauditlogsbydownload.md): Download the audit log for a date range as a CSV. Two flavors are available, selected via the `format` query parameter: - **`summary` (default when omitted)** — a flat-column CSV with one row per operation (its lifecycle entries are merged into one row) plus one row per non-operation event (login, user create, etc.). An operation created before `start_date` renders with its detail cells blank; widen the range to include its creation to populate them. Columns: Date, Operation ID, Event Name, Operation Type, Function, Amount, Token, CAIP-2, Source Wallet, Destination Wallet, Operation Status, Initiator, Approved By, Rejected By, Error Code, Error Message. Safe to import in Excel / Google Sheets without cell-size truncation. - **`forensics-zip`** — the legacy raw-JSON-metadata CSV (every audit log entry, with the full operation dump embedded in a `Metadata` column), wrapped in a single-entry ZIP archive. Use this when programmatic / jq tooling needs the full intent payload. The CSV bytes inside the ZIP are unchanged from prior releases. - [List most-recent audit log entries](https://vault.docs.blockdaemon.com/reference/listauditlogs.md): Returns paginated audit-log summary rows with the same column set as the `summary` CSV download. Each operation's lifecycle entries are merged into one row. Use `limit` and `cursor` to page through results; pass the `next_cursor` from each response as `cursor` on the next request. A missing `next_cursor` means there are no more rows. For bulk export use `/api/v2/audit-logs/download`. - [List batches](https://vault.docs.blockdaemon.com/reference/listbatches.md): Retrieve a list of transaction batches with optional filtering for in-progress batches. - [Get batch by ID](https://vault.docs.blockdaemon.com/reference/getbatch.md): Retrieve details of a specific transaction batch. - [Delete batch](https://vault.docs.blockdaemon.com/reference/deletebatch.md): Update the batch status to deleted. Once deleted, the batch cannot be recovered. - [Update batch](https://vault.docs.blockdaemon.com/reference/patchbatch.md): Only the status can be updated and it can only be updated to created. - [Download batch](https://vault.docs.blockdaemon.com/reference/getcoldbatchbydownload.md): Download the unsigned batch identified by batch ID for cold wallet signing. - [Upload signed batch](https://vault.docs.blockdaemon.com/reference/postsignedcoldbatchbyupload.md): Upload the signed version of the batch identified by batch ID. Once the required count of signatures is reached, the batch will be finalized. - [Upload cold pairing message](https://vault.docs.blockdaemon.com/reference/createcoldpairingmessagebyupload.md): Upload the cold wallet's pairing message after the cold wallet has received the pairing message from the hot wallet - [Download hot pairing message](https://vault.docs.blockdaemon.com/reference/gethotpairingmessagebydownload.md): Download the hot wallet's pairing message. This is the first step in pairing hot and cold wallets. - [Create Batch](https://vault.docs.blockdaemon.com/reference/cwpstartcreatebatch-1.md): Start an async Create Batch operation. Opens a signing batch for a master key; transactions are queued until the batch is finished or deleted. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Finish Current Batch](https://vault.docs.blockdaemon.com/reference/cwpstartfinishcurrentbatch-1.md): Start an async Finish Current Batch operation. Closes the open batch and submits partial signatures for all queued transactions. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Delete Current Batch](https://vault.docs.blockdaemon.com/reference/cwpstartdeletecurrentbatch-1.md): Start an async Delete Current Batch operation. Discards the open batch without signing. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create a new transfer](https://vault.docs.blockdaemon.com/reference/createtransfer.md): **Deprecated.** Use `POST /api/cwp/operations/start/makeTransaction` instead, which supports structured destinations, raw transactions, and Canton prepared submissions. - [Make Transaction](https://vault.docs.blockdaemon.com/reference/cwpstartmaketransaction-1.md): Start an async Make Transaction operation. With structured `Destination` (and optional `EVM` / chain-specific fields), creates, signs, and broadcasts the transaction when complete. With `RawTransaction` (and optional `TxHash` for Canton prepared submission), MPC signing only—the operation does **not** broadcast; the response includes `SignedTransaction` and the integrator must submit the signed bytes to the network. Requires `Source` as `AddressSpec` and `CAIP19`. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Generic Signing](https://vault.docs.blockdaemon.com/reference/cwpstartgenericsigning-1.md): Start an async Generic Signing operation. Signs arbitrary data (e.g. personal_sign, typed data). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Sign Raw Transaction (deprecated)](https://vault.docs.blockdaemon.com/reference/cwpstartsignrawtransaction-1.md): **Deprecated:** Use [`POST /operations/start/makeTransaction`](#/paths/~1operations~1start~1makeTransaction/post) with `Source` (`AddressSpec`), required `CAIP19`, and `RawTransaction` instead (same sign-only behavior: MPC signature only, no broadcast). This route uses a legacy flat payload (`MasterKeyName`, account-name `Source`, `Asset`). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Sponsor](https://vault.docs.blockdaemon.com/reference/cwpstartsponsor-1.md): Start an async Sponsor operation. Sponsors contract calls via EIP-7702 authorization. Requires `Data` and optionally `EIP7702Authorizations` in the EVM spec. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Consolidate Funds](https://vault.docs.blockdaemon.com/reference/cwpstartconsolidatefunds-1.md): Start an async Consolidate Funds operation. Moves funds from a sub-address back to the main address. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Fund Subaddresses](https://vault.docs.blockdaemon.com/reference/cwpstartfundsubaddresses-1.md): Start an async Fund Subaddresses operation. Distributes funds from the main address to multiple sub-addresses. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Generate Consolidation Data](https://vault.docs.blockdaemon.com/reference/cwpstartgenerateconsolidationdata-1.md): Start an async Generate Consolidation Data operation. Computes call data and EIP-7702 authorizations needed for a subsequent consolidation transaction. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create Allocation](https://vault.docs.blockdaemon.com/reference/cwpstartcreateallocation-1.md): Start an async Create Allocation operation. Creates a Canton allocation for a settlement workflow with executor, deadlines, and destination amounts. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Canton Enrollment](https://vault.docs.blockdaemon.com/reference/cwpstartcantonenrollment-1.md): Start an async Canton Enrollment operation. Enrolls an external party on the Canton ledger. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Canton Preapproval](https://vault.docs.blockdaemon.com/reference/cwpstartcantonpreapproval-1.md): Start an async Canton Preapproval operation. Creates a transfer preapproval for a Canton party. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [End Investor Onboarding Offer (Canton)](https://vault.docs.blockdaemon.com/reference/cwpstartcallchoiceonendinvestoronboardingoffer-1.md): Start an async operation to exercise a choice on a Canton end-investor-onboarding offer contract (operation type `call choice on end investor onboarding offer`). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Health check - live](https://vault.docs.blockdaemon.com/reference/getlive.md): Check if the server is up and running. - [Health check - ready](https://vault.docs.blockdaemon.com/reference/getready.md): Check if the server is ready to handle requests. - [Get address (deprecated)](https://vault.docs.blockdaemon.com/reference/cwpgetaddress-1.md): Deprecated: Use `POST /addresses/get` instead. Gets an address for the native asset in the specified master key and account. For a given (masterKey, account, symbol, testnet), a previously unused index can only take a value one greater than the maximal previously used index (zero if no previous calls). - [Get address](https://vault.docs.blockdaemon.com/reference/cwpgetaddresscaip2-1.md): Gets an address for the native asset of the chain identified by CAIP-2. For a given (masterKey, caip2, account), a previously unused index can only take a value one greater than the maximal previously used index (zero if no previous calls). - [Resolve address](https://vault.docs.blockdaemon.com/reference/cwpresolveaddress-1.md): Resolves a blockchain address to the master key, account, and address index that own it. - [Get Solana nonce account count](https://vault.docs.blockdaemon.com/reference/cwpgetsolanaaccountinfo-1.md): Returns the number of nonce accounts associated with the authority account on the given Solana chain. Send `CAIP2` and `Address` ([`AddressSpec`](#/components/schemas/AddressSpec)). Use either a literal `Address`, or `MasterKeyName`, `AccountName`, and `AddressIndex` together. - [Register Token](https://vault.docs.blockdaemon.com/reference/cwpstartregistertoken-1.md): Start an async Register Token operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Register Custom Chain](https://vault.docs.blockdaemon.com/reference/cwpstartregistercustomchain-1.md): Start an async Register Custom Chain operation. Registers a custom chain (CAIP-2) and its native asset (CAIP-19). The chain ID is derived from the native asset type. The operation is idempotent; registering an already-known chain updates it. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Unregister Token](https://vault.docs.blockdaemon.com/reference/cwpstartunregistertoken-1.md): Start an async Unregister Token operation. Removes a token previously registered with `registerToken`. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Unregister Chain](https://vault.docs.blockdaemon.com/reference/cwpstartunregisterchain-1.md): Start an async Unregister Chain operation. Removes a chain previously registered with `registerCustomChain`. Fails if any non-native tokens are still registered on the chain; unregister them first. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [List registered chains](https://vault.docs.blockdaemon.com/reference/cwplistchains-1.md): Returns all chains registered for the tenant (name, CAIP-2, testnet flag). - [Register a known chain](https://vault.docs.blockdaemon.com/reference/cwpregisterknownchain-1.md): Register a chain from the built-in chain registry. All chain metadata (name, native asset, coin type, decimals, etc.) is resolved from the CAIP-2 identifier. The call is idempotent: succeeds if the chain is already registered with identical data, but fails if existing data conflicts. - [List registered tokens](https://vault.docs.blockdaemon.com/reference/cwplisttokens-1.md): Returns all tokens registered for the tenant (symbol, decimals, CAIP-2, CAIP-19, chain name, testnet). - [Delete Token (deprecated)](https://vault.docs.blockdaemon.com/reference/cwpstartdeletetoken-1.md): **Deprecated:** Use [`POST /operations/start/unregisterToken`](#/paths/~1operations~1start~1unregisterToken/post) with required `CAIP19` instead. This route accepts legacy symbol-based input (`Symbol`, optional `ChainName`/`TestNetwork`); the server resolves those fields to CAIP-19 at start. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Associate to SPL Token](https://vault.docs.blockdaemon.com/reference/cwpstartassociatetospltoken-1.md): Start an async Associate to SPL Token operation. Creates an associated token account for the given SPL token. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Associate Nonce Account](https://vault.docs.blockdaemon.com/reference/cwpstartassociatenonceaccount-1.md): Start an async Associate Nonce Account operation. Creates a Solana nonce account for durable transactions. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Activate Stellar Address](https://vault.docs.blockdaemon.com/reference/cwpstartactivatestellaraddress-1.md): Start an async Activate Stellar Address operation. Funds and activates a Stellar address with the minimum XLM balance. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Search asset infos](https://vault.docs.blockdaemon.com/reference/cwpsearchassetinfos-1.md): Returns asset information for all tokens matching the filter. All filter fields are optional. An empty filter returns all registered assets. Filter by CAIP-2 chain ID, chain name, CAIP-19 asset type, symbol, or test network. - [Get token metadata](https://vault.docs.blockdaemon.com/reference/cwpgettokenmetadata-1.md): Returns the symbol and decimals for an asset (CAIP-19), looked up directly from the chain. Symbol and decimals are omitted if they could not be determined for this asset. - [Search operations](https://vault.docs.blockdaemon.com/reference/cwpsearchoperations-1.md): **Deprecated:** Prefer [`POST /operations/searchInfos`](#/paths/~1operations~1searchInfos/post) when you need a stable sort or pagination without unmarshalling full intents. Returns operations' intents matching the filter. If `Statuses` is omitted or empty, only operations that are not in a final state (`Succeeded` or `Failed`) are included. There is **no limit** field on the filter; this endpoint may return unbounded payloads. Matches are returned in **arbitrary order** (not ordered by creation time). The 200 response body is a **`ListOperationsResult`**: `Intents` is a JSON array of **stored intent objects** (standard `application/json` encoding of each intent struct). Each element matches one variant of **`IntentItem`** when the operation type is still startable over HTTP; use the object's **`OperationType`** field to select the variant. Older operation types that can no longer be started (for example `transfer`, `add ERC20 asset`) may still appear in responses but are omitted from the `IntentItem` union. This is not a base64 blob, `json.RawMessage`, or double-encoded JSON string layer. Returned intents include common metadata when present: `OperationType`, optional `OperationID` and `InitiatorID`, and server fields such as `Timestamp` and `InitiatorName` (see each variant under `IntentItem`). - [Search operation summaries](https://vault.docs.blockdaemon.com/reference/cwpsearchoperationinfos-1.md): Returns lightweight metadata. for operations matching `Filter`. Results are ordered by `CreatedTime` descending, with `OperationID` as a tiebreaker (also descending). If `Statuses` is omitted or empty, only operations that are not in a final state (`Succeeded` or `Failed`) are included. Use `Pagination.Size` to cap how many rows are returned per call. When more rows remain, `PaginationToken` is non-empty — pass its value as `Pagination.Token` on the next request. If `Pagination.Size` is zero or omitted, all matching rows are returned in one response and `PaginationToken` is empty. - [Get operation status](https://vault.docs.blockdaemon.com/reference/cwpgetoperationstatus-1.md) - [Get operation approval status](https://vault.docs.blockdaemon.com/reference/cwpgetoperationapprovalstatus-1.md) - [Get operation intent](https://vault.docs.blockdaemon.com/reference/cwpgetoperationintent-1.md): Returns the stored intent JSON for the operation. Startable operation types match one variant of [`IntentItem`](#/components/schemas/IntentItem), including `OperationType` and server-populated fields such as `Timestamp` and `InitiatorName` when present. Older operation types that can no longer be started over HTTP may still be returned but are omitted from the `IntentItem` union. - [Cancel an operation](https://vault.docs.blockdaemon.com/reference/cwpcanceloperation-1.md): Sets the operation state to Failed. Returns an error if the operation is already in a final state. - [Cancel an operation](https://vault.docs.blockdaemon.com/reference/cwpcanceloperationdelete-1.md): Sets the operation state to Failed. Returns an error if the operation is already in a final state. - [Update Config Restriction](https://vault.docs.blockdaemon.com/reference/cwpstartupdateconfigrestriction-1.md): Start an async Update Config Restriction operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Update Policy Restriction](https://vault.docs.blockdaemon.com/reference/cwpstartupdatepolicyrestriction-1.md): Start an async Update Policy Restriction operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Update Transaction Restriction](https://vault.docs.blockdaemon.com/reference/cwpstartupdatetransactionrestriction-1.md): Start an async Update Transaction Restriction operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Update Rates](https://vault.docs.blockdaemon.com/reference/cwpstartupdaterates-1.md): Start an async Update Rates operation. Sets USD spot rates or min/max bounds for assets used in policy evaluation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Get config restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetconfigrestrictions-1.md): Returns the tenant's config restrictions. These apply to config-related operations (e.g. adding tokens, registering blockchain networks). When a restriction applies, the specified approvers must approve before the operation can execute. - [Get policy restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetpolicyrestrictions-1.md): Returns the tenant's policy restrictions. These apply to policy-related operations (e.g. updating policy set, group, or restriction rules). When a restriction applies, the specified approvers must approve before the operation can execute. - [Get transaction restrictions](https://vault.docs.blockdaemon.com/reference/cwpgettransactionrestrictions-1.md): Returns the tenant's transaction restrictions. These apply to transaction operations (e.g. transfers). Each restriction has a filter with criteria (amount, fee, symbol, source, destination, etc.). A restriction applies when its filter matches — i.e. when all criteria are satisfied. When a restriction applies, the specified approvers must approve before the operation can execute. - [Get operation types for config restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetoperationtypesforconfig-1.md): Returns the operation types that are covered by config restrictions. Use these when configuring restrictions via `GET /restrictions/config`. - [Get operation types for policy restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetoperationtypesforpolicy-1.md): Returns the operation types that are covered by policy restrictions. Use these when configuring restrictions via `GET /restrictions/policy`. - [Get operation types for transaction restrictions](https://vault.docs.blockdaemon.com/reference/cwpgetoperationtypesfortransaction-1.md): Returns the operation types that are covered by transaction restrictions. Use these when configuring restrictions via `GET /restrictions/transaction`. - [Names used when filtering transactions by function](https://vault.docs.blockdaemon.com/reference/cwpgetrestrictiontransactionfunctionnames-1.md): Returns the names you can use when a transaction restriction should apply only to certain kinds of on-chain actions. Call this endpoint whenever you need the current list; it may change as the product evolves. - [Backup Master Key](https://vault.docs.blockdaemon.com/reference/cwpstartbackupmasterkey-1.md): Start an async Backup Master Key operation. Returns encrypted key shares for offline storage. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create Master Key](https://vault.docs.blockdaemon.com/reference/cwpstartcreatemasterkey-1.md): Start an async Create Master Key operation. Generates a new MPC master key via distributed key generation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create Account](https://vault.docs.blockdaemon.com/reference/cwpstartcreateaccount-1.md): Start an async Create Account operation. Creates a named account under an existing master key. When starting via this CWP endpoint, include `InitiatorID` set to a registered Vault user email so the Vault gateway can create the matching account record when it receives operation status updates. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Attach Master Key](https://vault.docs.blockdaemon.com/reference/cwpstartattachmasterkey-1.md): Start an async Attach Master Key operation. Attaches an externally generated master key using pairing messages. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Set ERS Public Key](https://vault.docs.blockdaemon.com/reference/cwpstartseterspublickey-1.md): Start an async Set ERS Public Key operation. Sets the RSA public key (PKIX DER) used for encrypted recovery shares. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [List accounts](https://vault.docs.blockdaemon.com/reference/cwplistaccounts-1.md): Returns all accounts registered for the tenant, across all master keys. - [List master keys](https://vault.docs.blockdaemon.com/reference/cwplistmasterkeys-1.md): Returns all master keys registered for the tenant. - [Register User](https://vault.docs.blockdaemon.com/reference/cwpstartregisteruser-1.md): Start an async Register User operation. Adds a user that can participate in approval workflows. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Set User Public Key](https://vault.docs.blockdaemon.com/reference/cwpstartsetuserpublickey-1.md): Start an async Set User Public Key operation. Associates a public key with a registered user. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Delete User](https://vault.docs.blockdaemon.com/reference/cwpstartdeleteuser-1.md): Start an async Delete User operation. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Reset User](https://vault.docs.blockdaemon.com/reference/cwpstartresetuser-1.md): Start an async Reset User operation. Resets a user's state (e.g. after device loss). Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Get User](https://vault.docs.blockdaemon.com/reference/cwpgetuserbyid-1.md): Get a user by ID. - [List Users](https://vault.docs.blockdaemon.com/reference/cwplistusers-1.md): List all registered users. - [Get All Group Members](https://vault.docs.blockdaemon.com/reference/cwpgetallgroupmembers-1.md): Returns all groups and their member user IDs. - [List Group Members](https://vault.docs.blockdaemon.com/reference/cwplistgroupmembers-1.md): List all members of a named group. - [List API Keys](https://vault.docs.blockdaemon.com/reference/cwplistapikeys-1.md): Returns all API keys (user ID and label only). - [Create API Key](https://vault.docs.blockdaemon.com/reference/cwpcreateapikey-1.md): Creates a new API key for the given user. The key is returned only once in this response — store it securely. - [Delete API Key](https://vault.docs.blockdaemon.com/reference/cwpdeleteapikey-1.md): Deletes the API key identified by the given user ID and label. Succeeds without error if the key does not exist (idempotent). - [Update Group](https://vault.docs.blockdaemon.com/reference/cwpstartupdategroup-1.md): Start an async Update Group operation. Adds or removes users from a named group. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Rename Group](https://vault.docs.blockdaemon.com/reference/cwpstartrenamegroup-1.md): Start an async Rename Group operation. Renames a group and updates all restriction references to the old group name. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Create a group](https://vault.docs.blockdaemon.com/reference/cwpcreategroup-1.md): Creates a new group with the given name. If a group with that name already exists, the operation succeeds without error (idempotent). - [Stake](https://vault.docs.blockdaemon.com/reference/cwpstartstake-1.md): Start an async Stake operation. Stakes assets to a validator on the specified chain. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Unstake](https://vault.docs.blockdaemon.com/reference/cwpstartunstake-1.md): Start an async Unstake operation. Unstakes from the specified validators. Status can be queried with [`GET /operations/id/{operationID}/status`](#/paths/~1operations~1id~1{operationID}~1status/get). - [Subscribe to events](https://vault.docs.blockdaemon.com/reference/cwpsubscribetoevents-1.md): Upgrades the connection to WebSocket. The server pushes `ClientEvent` messages; the client does not send data messages. Event types: - `operation_status_update` — an operation changed status. Payload: `OperationStatusUpdatePayload`. - `approver_onboarded` — an approver completed onboarding. Payload: `ApproverOnboardedPayload`. Delivery order of events is not guaranteed. To get the current state, query the server. - [Get USD prices](https://vault.docs.blockdaemon.com/reference/cwpgetusdprices-1.md): Returns the USD price for each of the given assets (CAIP-19). - [Set Up Public Key](https://vault.docs.blockdaemon.com/reference/cwpsetuppublickey-1.md): Registers the approver's ECDSA public key for the authenticated user, enabling them to sign and verify operation approvals. - [List Pending Approvals](https://vault.docs.blockdaemon.com/reference/cwplistapprovals-1.md): Returns the operations currently pending approval or confirmation for the given user. - [Approve Operation](https://vault.docs.blockdaemon.com/reference/cwpapproveoperation-1.md): Registers an approval of the specified operation by the given user. `IntentSignature` must be a signature of the operation's intent made with the user's private key. - [Reject Operation](https://vault.docs.blockdaemon.com/reference/cwprejectoperation-1.md): Registers a rejection of the specified operation by the given user. - [Register Device](https://vault.docs.blockdaemon.com/reference/cwpregisterdevice-1.md): Registers an Expo push notification device token for the user. Replaces any previously registered token for the same user. - [Unregister Device](https://vault.docs.blockdaemon.com/reference/cwpunregisterdevice-1.md): Removes the registered Expo push notification device token for the user. A no-op if no token is registered. - [Get on-chain balance](https://vault.docs.blockdaemon.com/reference/cwpgetonchainbalance-1.md): Returns the confirmed on-chain balance for the given master key, account, and asset (CAIP-19), aggregated across all derived addresses. The balance is a major-unit decimal string (e.g. `"0.25"`). - [Get spendable balance](https://vault.docs.blockdaemon.com/reference/cwpgetspendablebalance-1.md): Returns the spendable balance for the given master key, account, and asset (CAIP-19). - [Get on-chain token balances](https://vault.docs.blockdaemon.com/reference/cwpgetonchaintokenbalances-1.md): Returns the confirmed on-chain balance for all registered tokens, summed across all accounts. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Get spendable token balances](https://vault.docs.blockdaemon.com/reference/cwpgetspendabletokenbalances-1.md): Returns the spendable balance for all registered tokens, summed across all accounts. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Get on-chain token balances for account](https://vault.docs.blockdaemon.com/reference/cwpgetonchaintokenbalancesforaccount-1.md): Returns the confirmed on-chain balance for each token the account has addresses for. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Get spendable token balances for account](https://vault.docs.blockdaemon.com/reference/cwpgetspendabletokenbalancesforaccount-1.md): Returns the spendable balance for each token the account has addresses for. Tokens for which the balance could not be retrieved have an empty `Amount`. - [Pair with a WalletConnect dApp](https://vault.docs.blockdaemon.com/reference/cwpwalletconnectwalletconnectpair-1.md): Initiates a WalletConnect pairing using the URI from a dApp's QR code or deep link. The wallet will automatically negotiate supported chains and accounts with the dApp. - [Disconnect a WalletConnect session](https://vault.docs.blockdaemon.com/reference/cwpwalletconnectwalletconnectdisconnect-1.md): Disconnects an active WalletConnect session or cancels a pending pairing. The session must belong to the calling tenant. - [List active WalletConnect sessions](https://vault.docs.blockdaemon.com/reference/cwpwalletconnectwalletconnectlistsessions-1.md): Returns active WalletConnect sessions for the calling tenant. Results can be filtered by master key, account, and initiator user ID. The accountName filter also requires masterKeyName to be specified. ## Changelog - [Institutional Vault Release v3.7.2](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v372.md) - [Institutional Vault Release v3.7.1](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v371.md) - [Institutional Vault Release v3.7.0](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v370.md) - [Institutional Vault Release v3.6.0](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v360.md) - [Institutional Vault Release v3.5.0](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v350.md) - [Institutional Vault Release v3.4.2](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v342.md) - [Institutional Vault Release v3.4.1](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v341.md) - [Institutional Vault Release v3.4.0](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v340.md) - [Institutional Vault Release v3.3.1](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v331.md) - [Institutional Vault Release v3.3.0](https://vault.docs.blockdaemon.com/changelog/institutional-vault-release-v330.md)