Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API to list unconfirmed transactions by address UTXOs (Unspent Transaction Outputs) for a specified blockchain and network. It is useful for monitoring incoming or outgoing transactions that have not yet been confirmed on the blockchain, which can be critical for applications requiring real-time transaction status updates, such as wallets, payment processors, or blockchain explorers.

Practical examples include:

  • Tracking pending transactions for a specific wallet address.
  • Displaying unconfirmed transaction details in a user interface.
  • Triggering alerts or workflows when new unconfirmed transactions appear.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Bitcoin, Ethereum).
network The specific network within the blockchain (e.g., mainnet, testnet).
address The wallet address for which to list unconfirmed transaction UTXOs.
context Optional context string to correlate requests and responses.
limit Optional number to limit the number of results returned.
offset Optional number to specify the starting point for pagination of results.

Output

The node outputs an array of JSON objects representing unconfirmed transaction UTXOs related to the specified address. Each object contains detailed information about individual unconfirmed transactions, including transaction identifiers, amounts, and other relevant metadata.

If binary data were involved (not indicated here), it would typically represent raw transaction data or related files, but this node focuses on JSON transaction data only.

Dependencies

  • Requires an API key credential for the Crypto APIs REST API service.
  • The node depends on the external Crypto APIs service endpoint to fetch blockchain data.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing blockchain/network/address parameters will cause errors or empty results.
    • API rate limits may cause request failures; ensure your API plan supports the volume of requests.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • "Operation <operationName> not found": Indicates the requested operation is not defined in the API specification; verify the operation name.
    • API response errors (e.g., authentication failure, invalid parameters) will be propagated; check credentials and input values.
  • Resolutions:

    • Double-check all required parameters are provided and correctly formatted.
    • Ensure the API key credential is valid and has necessary permissions.
    • Handle pagination properly using limit and offset to avoid large result sets causing timeouts.

Links and References

Discussion