Crypto APIs

Overview

This node interacts with a comprehensive Crypto APIs REST API to retrieve detailed information about tokens by their contract address on EVM-compatible blockchains. Specifically, the "Get Token Details by Contract Address EVM" operation fetches metadata and details of a token deployed at a given smart contract address on a specified blockchain network.

Common scenarios where this node is beneficial include:

• Blockchain analytics platforms needing to display token metadata.
• Wallet applications verifying token details before displaying balances.
• DeFi dashboards aggregating token information from multiple networks.
• Developers building tools that require up-to-date token info for user interfaces or backend processing.

For example, a user can input the Ethereum blockchain, select the mainnet network, and provide a specific ERC-20 token contract address to retrieve its name, symbol, decimals, and other relevant data.

Properties

Output

The node outputs an array of JSON objects containing the token details fetched from the API. Each object typically includes fields such as token name, symbol, decimals, total supply, and possibly other metadata depending on the blockchain and token standard.

If the API returns binary data (not indicated in this operation), it would represent raw data related to the token, but this operation focuses on JSON metadata output.

Dependencies

• Requires an active connection to the Crypto APIs REST API service.
• 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 resolve API paths and parameters.
• No other external dependencies beyond standard Node.js modules and the Crypto APIs service.

Troubleshooting

• Operation Not Found Error: If the node throws an error stating the operation is not found, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and correctly loaded.
• Invalid Contract Address: Providing an incorrect or malformed contract address may result in API errors or empty responses. Verify the address format and correctness.
• Network or Blockchain Mismatch: Selecting a blockchain and network combination that does not support the contract address will cause failures or no data returned.
• Authentication Errors: Missing or invalid API credentials will prevent successful API calls. Confirm the API key is set up properly in n8n credentials.
• Continue On Fail Behavior: If enabled, the node will return error messages inside the output JSON instead of stopping execution, useful for batch processing.

Links and References

• Crypto APIs Documentation
• EVM Token Standards Overview
• n8n Documentation - Creating Custom Nodes