Overview
This node integrates with the Chainstream API to retrieve blockchain token data. It is useful for workflows that need to fetch detailed information about tokens on various blockchains, search tokens by query, or get multiple tokens at once. Practical examples include:
- Fetching metadata for a specific token by its address and chain ID.
- Searching tokens across multiple chains using keywords.
- Retrieving details for multiple tokens in bulk.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Key" |
| Query (q) | Search string used when performing a token search operation |
Output
The node outputs JSON data representing token information retrieved from the Chainstream API. The structure varies depending on the operation but generally includes token metadata such as addresses, names, symbols, and other blockchain-specific details.
If an error occurs during execution and the node is set to continue on failure, the output will contain an object with an error field describing the issue.
Dependencies
- Requires an API key credential for authenticating requests to the Chainstream API.
- Uses internal helper functions to make HTTP GET requests to endpoints like
/token/{chainId}/{tokenAddress},/token/{chainId}/multi, and/token/search. - No additional external dependencies beyond the Chainstream API and n8n's standard environment.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect chain ID or token address parameters may result in not found errors.
- Exceeding API rate limits could lead to request throttling errors.
Error messages:
- Errors returned from the API are captured and can be output if "Continue On Fail" is enabled.
- Typical error messages include authentication errors, invalid parameters, or network issues.
Resolution tips:
- Verify the API key is correctly configured and has necessary permissions.
- Double-check input parameters like chain IDs and token addresses for correctness.
- Use the "Continue On Fail" option to handle errors gracefully within workflows.
Links and References
- Chainstream API Documentation (hypothetical link for reference)
- n8n documentation on Creating Custom Nodes