Crypto APIs

Overview

This node interacts with the Crypto APIs REST API to retrieve blockchain fee recommendations specifically for UTXO-based blockchains. It allows users to get suggested transaction fees based on the selected blockchain and network, which is useful for optimizing transaction costs and confirmation times.

Common scenarios include:

• Automatically fetching recommended fees before sending a cryptocurrency transaction.
• Adjusting wallet or application settings dynamically based on current network fee conditions.
• Monitoring fee trends for UTXO blockchains like Bitcoin or Litecoin.

For example, a user can select "bitcoin" as the blockchain and "mainnet" as the network to get up-to-date fee recommendations for Bitcoin transactions.

Properties

Output

The node outputs an array of JSON objects containing the fee recommendation data returned by the Crypto APIs service. The exact structure depends on the API response but typically includes fields such as recommended fee rates for different priority levels (e.g., slow, average, fast) and possibly other metadata related to UTXO fee estimation.

If the API returns binary data (not typical for this operation), it would represent raw fee data or related information, but this node primarily deals with JSON responses.

Dependencies

• Requires an active connection to the Crypto APIs REST API.
• Needs an API key credential configured in n8n for authenticating requests.
• Relies on the bundled OpenAPI specification file (2024-12-12-final.json) for operation definitions.
• Uses internal helper functions to perform HTTP requests to the Crypto APIs endpoints.

Troubleshooting

• Operation not found error: If the specified operation is not recognized, ensure that the operation name matches exactly and that the bundled OpenAPI spec file is present and correctly loaded.
• Missing required parameters: The blockchain and network properties are mandatory; missing these will cause errors.
• API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
• Network or connectivity issues: Ensure that the n8n instance can reach the Crypto APIs endpoint without firewall or proxy restrictions.
• Unexpected API response: If the API changes or returns unexpected data, updating the bundled OpenAPI spec or checking the API documentation may be necessary.

Links and References

• Crypto APIs Documentation
• UTXO Fee Recommendations API Reference
• n8n Documentation on Creating Custom Nodes