Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API service to list the latest mined blocks' Unspent Transaction Outputs (UTXOs) for a specified blockchain and network. It is useful in scenarios where users want to monitor recent block data, analyze UTXO sets for wallet balances, or track blockchain activity for analytics or auditing purposes.

Practical examples include:

  • Fetching the most recent UTXOs on Bitcoin mainnet to update wallet balances.
  • Monitoring newly mined blocks on Ethereum test networks for development or testing.
  • Integrating blockchain data into dashboards that display real-time mining activity.

Properties

Name Meaning
network The specific blockchain network to query, e.g., "mainnet", "testnet".
blockchain The blockchain protocol to target, e.g., "bitcoin", "ethereum".
context Optional string to correlate or label the request context for tracking or logging.
count Optional number specifying how many of the latest mined blocks' UTXOs to retrieve.

Output

The node outputs an array of JSON objects representing the UTXOs from the latest mined blocks according to the specified parameters. Each JSON object corresponds to a UTXO entry containing details such as transaction identifiers, output indices, amounts, and addresses involved.

If the node supports binary data output, it would typically represent raw blockchain data or serialized transaction information; however, based on the static analysis, this node primarily outputs structured JSON data.

Dependencies

  • Requires an active connection to a cryptocurrency API service via an API key credential configured in n8n.
  • The node depends on a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically resolve API endpoints and parameters.
  • No additional external dependencies beyond standard Node.js modules and the n8n workflow environment.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Incorrect blockchain or network values may result in no data returned or errors from the API.
    • Providing an invalid count value (e.g., negative numbers) might lead to unexpected results or API rejections.
  • Error Messages:

    • "Operation <operationName> not found": Indicates the requested operation is not defined in the API spec or was misspelled. Verify the operation name matches exactly.
    • API request errors due to network issues or rate limits will be propagated; ensure stable internet connectivity and valid API usage quotas.
    • If continueOnFail is enabled, errors are returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion