Crypto APIs

Overview

This node interacts with the Crypto APIs REST API to retrieve historical token data associated with a specific blockchain address on an EVM-compatible network. Specifically, the "List Tokens By Address Synced EVM" operation fetches tokens that have been synced for a given wallet address, providing insight into the tokens held or interacted with by that address over time.

Common scenarios where this node is beneficial include:

• Portfolio tracking: Users can monitor all tokens historically linked to a wallet.
• Auditing and compliance: Reviewing token holdings and transactions for regulatory or security purposes.
• Data aggregation: Collecting token data for analytics or reporting tools.

For example, a user might input an Ethereum address and receive a list of all ERC-20 tokens that have been associated with that address, including pagination support via limit and startingAfter parameters.

Properties

Output

The node outputs a JSON array where each element represents a token associated with the specified address on the selected blockchain and network. Each JSON object typically contains details about the token such as its identifier, symbol, name, balance, and other metadata provided by the Crypto APIs service.

If the API supports binary data output (not indicated here), it would be summarized accordingly, but this operation primarily returns structured JSON data.

Dependencies

• Requires an active connection to the Crypto APIs REST API.
• Needs an API key credential configured in n8n to authenticate requests.
• The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically map operations and parameters.
• No additional external dependencies beyond standard Node.js modules and the Crypto APIs service.

Troubleshooting

• Operation Not Found Error: If the specified operation is not found in the API spec, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and up-to-date.
• Invalid Address or Network: Providing an incorrect or unsupported blockchain, network, or address may result in empty responses or errors. Verify inputs carefully.
• API Rate Limits or Authentication Errors: Ensure the API key credential is valid and has sufficient permissions. Handle rate limits by implementing retries or adjusting request frequency.
• Pagination Issues: Incorrect use of limit and startingAfter parameters may cause incomplete data retrieval. Use these parameters according to the API documentation to paginate through large datasets.

Links and References

• Crypto APIs Documentation
• EVM-Compatible Networks Overview
• n8n Documentation - Creating Custom Nodes