Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a Crypto APIs REST API to retrieve blockchain fee recommendations specifically for EVM-compatible blockchains. It is useful when you want to dynamically fetch recommended transaction fees (gas prices) for Ethereum and similar networks to optimize transaction costs and speed.

Typical use cases include:

  • Automatically adjusting gas fees in smart contract transactions.
  • Displaying current network fee recommendations in dashboards.
  • Integrating fee data into automated workflows that send blockchain transactions.

For example, you can use this node to get the current recommended gas price on the Ethereum mainnet or any other supported EVM chain before submitting a transaction.

Properties

Name Meaning
blockchain The name of the blockchain network (e.g., "ethereum", "polygon") for which to get fees.
network The specific network environment (e.g., "mainnet", "ropsten") within the blockchain.
context Optional string to specify additional context for fee recommendation (usage depends on API).

Output

The node outputs JSON data containing the fee recommendations returned by the Crypto APIs service. This typically includes suggested gas prices or fee tiers (e.g., slow, average, fast) relevant to the specified blockchain and network.

The output is an array of JSON objects, each representing a fee recommendation response from the API.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • Relies on the external Crypto APIs service endpoint defined in the bundled OpenAPI specification file.

Troubleshooting

  • Common issues:

    • Incorrect or missing blockchain/network parameters may cause the API to return errors or empty results.
    • Network connectivity problems or invalid API credentials will result in authentication or request failures.
    • If the operation ID is not found in the API spec, the node throws an error indicating the operation was not found.
  • Error messages:

    • Operation <operationId> not found: Indicates a mismatch between the requested operation and the loaded API specification. Verify the operation name and resource selection.
    • API request errors usually contain descriptive messages from the Crypto APIs service; check your API key validity and parameter correctness.

Links and References

Discussion