EVM chains support transfers to a single address, while UTXO chains support transfers to one or more addresses. You can transfer funds in either native coin or token in a single request.

Transactions from v2 wallets are screened by Liminal Firewall (if enabled). It performs compliance checks and provides outcomes before broadcasting to the blockchain. If your organisation has a Travel Rule policy enabled in Firewall, include the travelRule object in the request body to avoid transaction failure. If the policy is disabled, you can skip this object.

Accepted parameter values:

The transactions.recipients.address[] parameter must have a valid address length ( > 0). It will not accept any null value or empty String value.
The data type of transactions.recipients.amount[] is updated to String and must be a positive decimal string. It will not accept empty string, null, or number value.

Refer to the Create transaction requests API instead if you are using the v1 wallet. While all liminal supported chains support firewall for Mobile MPC Wallets, please refer to the latest supported chains for hot V2 wallets supporting firewall.

📘
Note

For transactions to be fully signed and broadcast, ensure that the transaction execution job is running on your Liminal Express server.

This API is responsible only for the transactions originating from the v2 hot wallets. Refer to this guide to learn how to set up a v2 hot wallet using Liminal firewall.

👍
Tip

Use the Verify Addresses API to validate the destination addresses before using the API.

Refer to wallet versions: v1 & v2 to learn more about the types of wallet versions and their respective supported chains.

❗️
Ensure to enter the transactions.recipients.address[] and transactions.recipients.amount[] values accurately. There may be a breaking change in the API request if you are using number value. Ensure you are using Liminal Express SDK v1.3.10.

201OK

400Validation error

422Unprocessable Entity