Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to list confirmed transactions by address UTXOs (Unspent Transaction Outputs) for a specified blockchain and network. It is useful for users who want to retrieve detailed transaction data related to a specific wallet address, particularly focusing on confirmed transactions that have unspent outputs.

Common scenarios include:

  • Monitoring wallet activity by fetching all confirmed transactions associated with an address.
  • Building blockchain explorers or analytics tools that require up-to-date transaction data.
  • Auditing or reconciling wallet balances by analyzing UTXOs.

For example, a user can specify a Bitcoin blockchain and mainnet network along with a wallet address to get a list of all confirmed transactions with their UTXOs, optionally limiting the number of results or sorting them in ascending or descending order.

Properties

Name Meaning
blockchain The blockchain to query (e.g., Bitcoin, Ethereum).
network The network within the blockchain (e.g., mainnet, testnet).
address The wallet address for which to list confirmed transactions by UTXOs.
context Optional context string to correlate responses with requests.
limit Optional number to limit the number of returned transactions.
startingAfter Optional cursor for pagination to start after a specific transaction ID.
sortingOrder Optional order to sort the results: "ascending" or "descending".

Output

The node outputs a JSON array where each item represents a confirmed transaction containing UTXO details related to the specified address. Each JSON object includes transaction metadata and the list of unspent outputs.

If binary data were involved, it would be summarized here, but this operation deals solely with JSON transaction data.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n for authentication.
  • No additional external dependencies beyond the Crypto APIs service.

Troubleshooting

  • Common issues:

    • Invalid or missing blockchain/network/address parameters will cause errors.
    • API rate limits may result in request failures; consider using pagination (limit and startingAfter) to manage large datasets.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "Operation ... not found": Indicates the requested operation is not recognized; ensure the correct operation name is selected.
    • API errors from Crypto APIs will be passed through; check the error message for details such as invalid credentials or malformed requests.

To resolve errors, verify all required parameters are correctly set, ensure valid API credentials, and handle pagination properly when dealing with large result sets.

Links and References

Discussion