Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve detailed information about a Solana token by its contract address. It is useful for blockchain developers, analysts, or enthusiasts who want to fetch metadata and details of tokens deployed on the Solana network using their contract addresses.

Typical use cases include:

  • Verifying token details before transactions.
  • Displaying token metadata in dashboards or wallets.
  • Automating token data retrieval for portfolio management or analytics.

For example, given a Solana contract address, this node can return the token's name, symbol, decimals, and other relevant attributes.

Properties

Name Meaning
network The Solana network to query (e.g., mainnet, testnet).
contractAddress The specific contract address of the Solana token whose details are to be retrieved.
context Optional additional context string to correlate requests or responses (user-defined).

Output

The node outputs an array of JSON objects containing the token details fetched from the Crypto APIs service. Each object includes fields such as token metadata, identifiers, and possibly other blockchain-specific attributes related to the queried contract address.

No binary data output is produced by this operation.

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 resolve API paths and parameters.

Troubleshooting

  • Operation not found error: If the specified operation cannot be found in the internal API spec, ensure the "operation" parameter is correctly set to "Get Token Details by Contract Address Solana".
  • Missing required parameters: The network and contractAddress properties are mandatory; missing these will cause errors.
  • API request failures: Network issues or invalid API credentials may cause request failures. Verify API key validity and network connectivity.
  • Continue on Fail: If enabled, errors during execution will be returned as JSON error messages instead of stopping the workflow.

Links and References

Discussion