Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a blockchain-related API to estimate the gas limit required for transferring native coins on EVM-compatible blockchains. It is useful when you want to programmatically calculate how much gas (transaction fee) will be needed before sending a native coin transfer transaction, helping to avoid failed transactions due to insufficient gas.

Typical use cases include:

  • Wallet applications estimating fees before sending transactions.
  • Automated scripts or workflows that prepare and send blockchain transactions.
  • Blockchain explorers or analytics tools providing fee estimations.

For example, if you want to send Ether on Ethereum or BNB on Binance Smart Chain, this node can estimate the gas limit needed for that transfer based on the sender, recipient, and amount.

Properties

Name Meaning
blockchain The blockchain network to use (e.g., Ethereum, Binance Smart Chain).
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to correlate requests or for logging purposes.
JSON Body A collection of optional parameters:
- additionalData Extra data to include in the transaction (optional).
- amount Amount of native coin to transfer (optional).
- recipient Address of the recipient wallet (optional).
- sender Address of the sender wallet (optional).

Output

The output is a JSON array where each item contains the response from the API call estimating the gas limit. The exact structure depends on the API but typically includes fields such as:

  • Estimated gas limit for the native coin transfer.
  • Possibly other metadata related to the estimation.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for the Crypto APIs service.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically configure operations.
  • Network access to the Crypto APIs REST endpoint is necessary.

Troubleshooting

  • Operation not found error: If the specified operation is not found in the API spec, ensure the operation name matches exactly and the node version is up to date.
  • Missing required parameters: Make sure all required properties like blockchain and network are provided.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network issues: Check internet connectivity and firewall settings that might block API requests.
  • Invalid addresses or amounts: Ensure that sender and recipient addresses are valid blockchain addresses and amounts are properly formatted strings.

Links and References

Discussion