Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve historical synced wallet addresses on a specified blockchain network. Specifically, the "List Synced Addresses" operation under the "addresses-historical" resource fetches a list of wallet addresses that have been synchronized historically for a given blockchain and network.

Common scenarios where this node is beneficial include:

  • Auditing or monitoring wallet addresses that have been tracked over time on a blockchain.
  • Building dashboards or reports that require historical address data.
  • Integrating blockchain address history into broader workflows for compliance or analytics.

For example, you could use this node to list all Bitcoin addresses synced on the mainnet, optionally limiting the number of results or paginating through them.

Properties

Name Meaning
blockchain The blockchain to query (e.g., Bitcoin, Ethereum).
network The specific network of the blockchain (e.g., mainnet, testnet).
context Optional context string to correlate responses with requests.
limit Optional maximum number of synced addresses to return.
startingAfter Optional pagination cursor to start listing after a specific address ID or token.

Output

The node outputs an array of JSON objects representing the synced wallet addresses retrieved from the Crypto APIs service. Each object corresponds to one address entry with its associated details as provided by the API.

If the API supports binary data output for this operation (not indicated in the code), it would typically represent raw data related to addresses, but here only JSON data is returned.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n for authentication.
  • Uses the Crypto APIs OpenAPI specification file (2024-12-12-final.json) bundled with the node for request construction.
  • No additional external dependencies beyond standard Node.js modules and n8n workflow utilities.

Troubleshooting

  • Operation Not Found Error: If the node throws Operation <name> not found, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and correctly loaded.
  • Missing Required Parameters: The blockchain and network properties are required; omitting them will cause errors.
  • API Request Failures: Network issues or invalid API credentials can cause request failures. Verify your API key and network connectivity.
  • Pagination Issues: Using startingAfter incorrectly may result in empty or repeated results. Use the value returned from previous calls for proper pagination.

Links and References

Discussion