Request
coin code
transaction ID (unique identifier of a transaction request, which must correspond to a client’s transaction; UUID should be used and the length should be equal to or less than 120 characters)
transaction amount in decimal places (e.g. one bitcoin is divisible to eight decimal places, and 100000000 represents 1 BTC)Account Model: this parameter is requiredUTXO Model: this parameter is optional. The transaction sending amount will be based on the
to_address_details
parameter if the amount
is zero or emptyAccount Model: this parameter is requiredUTXO Model: this parameter is optional, the input will be selected based off the
extra_parameters
parameter if the from_address
is empty or not passed. The from_address
will also be used as the change address of UTXO transactions when utxo_change_address not specified in extra_parametersto address
list of addresses used for receiving coins associated with the UTXO model; this value must be a JSON string and has a parameter type that fits.
Please note that the
Please note that the
to_address_details
parameter and amount
parameter are alternative. Please set the amount
parameter to 0 or leave it empty when using the to_address_details
parameter.Sample
transaction fees per byte; applicable to UTXO model; use either fee or fee_amount for UTXO model
If you have previously called the
estimate_fee
API to obtain an estimated fee for UTXO transactions before creating the transaction, please use the fee_amount
parameter instead of fee
to specify the transaction fee. Otherwise, it will re-estimate the transaction fee based on the fee
parameter when creating the transaction.gas price; applicable to ETH; unit: wei
gas limit, applicable to ETH
action type,
100: TRANSFER (default);
200: CONTRACT_CALL
UTXO Model:Web3 wallet:
- input_selection: inputs to be excluded and included in transactions associated with the UTXO model; inputs must be in correspondence with from_address (if specified); it must be a JSON string and has a structure that fits InputSelection
- inputs_to_spend: UTXO you want as input. Please note that the length of the list of UTXOs should be less than or equal to 100.
- tx_hash: Transaction tx_hash
- vout_n: UTXO index
- inputs_to_exclude: UTXO you don’t want as input
- tx_hash: Transaction tx_hash
- vout_n: UTXO index
- utxo_change_address: the change address for UTXO transactions. if parameter from_address passed and utxo_change_address not passed, from_address will be used as the change address. otherwise, the permanent address (SegWit) will be used as the change address
Sample
- calldata: request data associated with an EVM transaction; When deploying a new contract, the
to_address
parameter should be set to0x0000000000000000000000000000000000000000
. Please note that when usingcalldata
, thegas_limit
parameter should be set to an appropriate value based on the data being sent and the contract’s execution requirements.
Sample
- instructions: request data associated with a Solana transaction. This parameter is in JSON format and contains a list of instructions. Each instruction includes the following parameters:
- accounts: a list of accounts associated with Solana contract, each of which has the following attributes:
- pubkey: account address. If the account is signer,
pubkey
needs to match thefrom_address
parameter. - is_signer: boolean value indicating whether the account can sign transactions.
- is_writable: boolean value indicating whether the account can be modified.
- pubkey: account address. If the account is signer,
- data: data used for calling Solana contract.
- program_id: contract address. when calling a Solana contract, the
to_address
parameter needs to match theprogram_id
parameter. If multiple contracts are being called, then theto_address
parameter should match theprogram_id
parameter of the first instruction.
- accounts: a list of accounts associated with Solana contract, each of which has the following attributes:
Sample
transaction fee; applicable to UTXO model; use either fee or fee_amount for UTXO model
The remark to withdraw. The length should be less than 2048 characters
How the transaction utilizes the gas station, 0: no refueling(default); 1: passive use of the gas station; 2: active use of the gas station.
This parameter is used when you’ve activated the gas station service and use the gas station to support the transaction fee for MPC transactions.
This parameter is used when you’ve activated the gas station service and use the gas station to support the transaction fee for MPC transactions.
The gas station will definitely refuel for the transaction when in active use, while for passive use, refueling by the gas station occurs only when the address balance is insufficient for transaction fees.
Please note that due to the TRON chain’s fee delegation mechanism, only no refueling and active use of the gas station are supported for the TRON chain; passive use of the gas station is not supported.
Please note that due to the TRON chain’s fee delegation mechanism, only no refueling and active use of the gas station are supported for the TRON chain; passive use of the gas station is not supported.
Needed when you withdraw XRP
Response
request successful or failed
Feel free to share your feedback to improve our documentation!