Consolidate wallet assets

You can transfer cryptocurrency assets from your customer addresses within your v2 deposit wallet and consolidate them into a destination wallet. You can call this API once and consolidate funds from a single or multiple addresses. To learn more about consolidation, see Digital asset consolidation. To learn about different use cases of this API, see Consolidate wallet assets API.

Please note the following when making an API request:

  1. Consolidate Single Address for non-UTXO chain: Use this option for native coin consolidation.
  2. Consolidate single token for Non-UTXO chains: Use this option to consolidate tokens. Currently, only one token consolidation is supported per API request.

Refer to this guide to learn more.

📘

Note

  1. The info array in the API success response includes objects containing addresses and responses for asset consolidation features for those addresses, such as insufficient balance, exceeded fee limits, and others.
  2. For the transaction to be fully signed and broadcast, ensure that the transaction execution job is running on your Liminal Express server.
  3. The error 400: Nothing to consolidate is only applicable when consolidating multiple addresses for non-UTXO chains.
  4. The API has a rate limit of 15 seconds per request.
  5. While all liminal supported chains support firewall for Mobile MPC Wallets, please refer to the latest supported chains for hot V2 wallets supporting firewall.
👍

Tip

  1. Use the Retrieve list of addresses for consolidation API to retrieve a list of addresses eligible for consolidation for a respective chain.
  2. This API is applicable only for transactions originating from v2 hot wallets. Refer to the Set up v2 hot wallets with Liminal Firewall guide to set it up for your organisation.
  3. Refer to the Wallet v1 and v2 section to learn more about them and their respective supported chains.
Path Params
string
required

The unique identifier of the hot deposit wallet.

Body Params
wallet
object
required
transactions
object
required
Headers
string
enum
Defaults to application/json; charset=utf-8

Generated from available response content types

Allowed:
Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json; charset=utf-8
application/json