Crypto APIs

Overview

This node operation, List Confirmed Transactions By Address UTXO Historical, retrieves historical confirmed transactions associated with a specific cryptocurrency address on a given blockchain and network. It is useful for users who want to analyze past transaction activity of an address, audit wallet history, or track funds movement over time.

Typical use cases include:

• Blockchain analysts auditing transaction histories.
• Wallet services displaying past confirmed transactions to users.
• Developers building tools that require historical UTXO (Unspent Transaction Output) data for addresses.

For example, you could use this node to fetch all confirmed Bitcoin transactions for a particular address on the Bitcoin mainnet, sorted in ascending order, limiting results to 50 entries.

Properties

Output

The output is a JSON array where each element represents a confirmed transaction related to the specified address. Each transaction object contains detailed information as provided by the underlying Crypto APIs service, typically including transaction IDs, block confirmations, timestamps, inputs, outputs, and amounts.

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

Dependencies

• Requires an active connection to the Crypto APIs REST API service.
• Needs a valid API authentication token configured in n8n credentials to authorize requests.
• No additional environment variables are explicitly required beyond standard API key setup.

Troubleshooting

• Common issues:

  • Invalid or missing blockchain/network/address parameters will cause request failures.
  • Exceeding rate limits imposed by the Crypto APIs service may result in errors or throttling.
  • Pagination parameters (limit, startingAfter) must be used carefully to avoid empty or repeated results.

• Error messages:

  • "Operation ... not found": Indicates the internal mapping failed; usually a configuration or version mismatch.
  • API errors returned from Crypto APIs (e.g., invalid address format, unsupported blockchain) should be checked against the API documentation.

• Resolutions:

  • Verify all required parameters are correctly set.
  • Ensure the API key credential is valid and has sufficient permissions.
  • Use pagination parameters properly to navigate large datasets.

Links and References

• Crypto APIs Documentation
• Understanding UTXO Model
• n8n Documentation on Creating Custom Nodes