Estimate Transaction Fees
Estimate transaction fees
If you've set up your API Key when initializing your LAM, you'll need to include it as a header along with the api user header. For more details, see step 5 of the get started documentation.
(required) Username of a registered API User
The account's name.
The amount to be sent, in the currency's lowest unit. For Smart Contract interaction, use "0" instead of null
nullPattern: ^[0-9]*(\.[0-9]+)?$coin specific data
nullThe recipient's address.
The transaction's processing speed.
attributes of the transaction to estimate
nullThe estimated max fees for the requested transaction attributes, in base units. We recommend using this amount as max_fee when creating a transaction request through POST /transactions for the same transaction attributes. Max fees represent the highest possible fee amount you will pay to broadcast this transaction. The final fees, calculated once the transaction is approved by the last Operator, might be lower, but will never exceed that amount. See https://help.vault.ledger.com/developer-portal/content/transactions/tx/ for details
Network fees can fluctuate between the creation of a transaction request and the submission of the transaciton to the network, after all the approvals have been collected. Ledger Vault adds a buffer to the network fees required for the selected transaction speed. See https://help.vault.ledger.com/developer-portal/content/transactions/tx/
Invalid transaction parameters