Overview
This node integrates with the Chainstream API to retrieve information about blockchain tokens. Specifically, the "Token - Get Many" operation fetches details for multiple tokens on a specified blockchain chain by their addresses. This is useful when you want to gather data about several tokens in bulk, such as their metadata or status, without making individual requests for each token.
Practical examples:
- Fetching token details for a list of token addresses on Ethereum or other supported chains.
- Aggregating token information for portfolio analysis or reporting.
- Validating multiple token contracts before processing transactions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports only "API Key". |
| Chain ID | The blockchain network identifier (e.g., Ethereum mainnet, Binance Smart Chain). Choose from a list or specify via expression. Required. |
| Token Addresses | Comma-separated string of token contract addresses to query. |
| Query | A search query string (not used in "Get Many" but available for other operations). |
Output
The node outputs an array of JSON objects, each representing detailed information about a token corresponding to the requested addresses on the specified chain. The exact structure depends on the Chainstream API response but typically includes token metadata such as name, symbol, decimals, and contract address.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Chainstream API.
- An API key credential must be configured in n8n to authenticate requests.
- The node dynamically loads available blockchain chains from the API to populate the Chain ID options.
Troubleshooting
- Empty or invalid token addresses: Ensure that the "Token Addresses" property contains valid, comma-separated blockchain token contract addresses.
- Invalid Chain ID: Select a valid chain from the dropdown or provide a correct chain identifier expression.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- API request failures: Network issues or API downtime can cause errors; check connectivity and Chainstream service status.
- Error messages: If the node throws an error with a message from the API, review the message for clues (e.g., invalid parameters) and adjust inputs accordingly.
- Use the "Continue On Fail" option to handle partial failures gracefully when processing multiple tokens.
Links and References
- Chainstream API Documentation (for detailed API endpoints and data structures)
- n8n Expressions Documentation (for using expressions in properties)