Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve blockchain-related data. Specifically, for the "blocks" resource and the "Get Last Mined Block UTXOs" operation, it fetches the Unspent Transaction Outputs (UTXOs) of the most recently mined block on a specified blockchain network.

This is useful in scenarios where you want to analyze or monitor the latest confirmed transactions that have not yet been spent, such as for wallet balance calculations, transaction tracking, or blockchain analytics.

Example use cases:

  • A cryptocurrency wallet application fetching the latest UTXOs to update user balances.
  • Blockchain explorers displaying recent unspent outputs for transparency.
  • Automated trading bots analyzing fresh blockchain data for decision making.

Properties

Name Meaning
blockchain The specific blockchain network to query, e.g., Bitcoin, Ethereum, etc.
network The network type within the blockchain, e.g., mainnet, testnet, ropsten, etc.
context Optional additional context or metadata to pass along with the request (usage varies).

Output

The node outputs an array of JSON objects representing the UTXOs of the last mined block on the specified blockchain network. Each object contains details about individual unspent transaction outputs, such as transaction IDs, output indices, amounts, and addresses involved.

If the node encounters errors and "Continue On Fail" is enabled, it outputs JSON objects containing an error field with the error message.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Crypto APIs REST API via an API key credential configured in n8n.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically determine API paths and parameters.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Incorrect or missing blockchain or network parameter values may cause the API to return errors or empty results.
    • Network connectivity problems or invalid API credentials will prevent successful requests.
    • If the OpenAPI spec file is missing or corrupted, the node will fail to resolve the operation.
  • Error messages:

    • "Operation <operationName> not found" indicates the requested operation is not defined in the bundled API spec; ensure correct operation name and node version.
    • API errors returned from Crypto APIs will be surfaced as error messages; verify your input parameters and API key validity.
  • Resolutions:

    • Double-check the spelling and casing of blockchain and network inputs.
    • Verify your API key credential is correctly set up and has necessary permissions.
    • Ensure the node's bundled files are intact and the node is up to date.

Links and References

Discussion