Calculates an approximate fee by Asset ID for a planned transaction before it is submitted. This endpoint supports all transaction types: single transfer, multi transfer, gas sponsorship, and batch transfer. Use this endpoint to estimate costs and validate transaction feasibility prior to execution.
The unique identifier of the vault from which the transaction will originate.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
Amount to transfer. Required for Single and Gas sponsorship transfers.
The identifier of the asset to transfer. (Required for Single, Gas sponsorship and Multiple transfers).
Fee payer (sponsor) address . Required for Batch and Gas sponsorship transfers.
Asset ID of the fee payer . Required for Batch transfer.
Fee priority - slow, standard, fast. Not applicable for Tron and Solana.
Sender address. Required for Single, Batch and Gas sponsorship transfers.
Strategy for preparing transaction - minimize_dust or optimize_size. (used for UTXO transactions).
Destination addresses with amounts. Required for Multiple and Batch transfers.
Address of the destination. Required for Multiple and Batch transfers.
Amount to transfer. Required for Multiple and Batch transfers.
Asset ID for this destination. Required for Batch transfer, provide assetId inside each recipient object instead.
The recipient's address. Required for EVM transactions - Single and Gas sponsorship transfers.
Type of transaction: single, multiple, batch. Gas sponsorship transfer use transactionType: single.
Sender's vault account ID.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Vaultody and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
The message of the error if such occurred.
The calculated fee.
For UTXO based transactions. The max amount you can send from the vault account.
cb233681a8ee35665296c1824c1f67bc46691788
PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
1681885776
zYgKeueoOq
{
"context": "yourExampleString",
"data": {
"item": {
"amount": "0.001",
"assetId": "6995822ce883e61317b3d6b6",
"feePayer": "0x0c3f01e4b2aae7c258f044c4cb64354f487abe8b",
"feePayerAssetId": "6995822ce883e61317b3d6b6",
"feePriority": "slow",
"fromAddress": "0x463ebfb8eb88b41fd57952a407c14409fc0fb9a4",
"prepareStrategy": "optimize_size",
"recipients": [
{
"address": "0x9e1046549484c5e17b00fb40beda0abbdf9cfca9",
"amount": "0.001",
"assetId": "6995822ce883e61317b3d6b6"
}
],
"toAddress": "0xd2070342a1a5ce24930ec6582b3db846458525a0",
"transactionType": "single",
"vaultAccountId": "69c28b729d1ca8000714911a"
}
}
}
{
"apiVersion": "2026-03-20",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"errorMessage": "INSUFFICIENT_FUNDS",
"feeInNative": "0.00001698",
"maxAmount": "10"
}
}
}