Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve blockchain-related data. Specifically, for the "addresses-latest" resource and the "Get Address Balance Solana" operation, it fetches the balance of a given Solana blockchain address on a specified network.

Common scenarios where this node is beneficial include:

  • Monitoring wallet balances on the Solana blockchain.
  • Integrating Solana address balance checks into automated workflows.
  • Building dashboards or alerts based on Solana wallet balances.

Practical example:

  • A user wants to check the current SOL token balance of a specific wallet address on the Solana mainnet or testnet as part of a larger crypto portfolio management workflow.

Properties

Name Meaning
network The Solana network to query (e.g., mainnet, testnet).
address The Solana wallet address whose balance is to be retrieved.
context Optional context string to correlate or tag the request (usage depends on API support).

Output

The node outputs JSON data representing the balance information of the specified Solana address. The exact structure depends on the API response but typically includes fields such as the amount of SOL tokens held by the address.

If the node supports binary data output, it would represent any associated binary content; however, in this operation, only JSON data related to the address balance is returned.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n for authentication.
  • 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

  • Common issues:

    • Incorrect or missing network or address parameters will cause the API call to fail.
    • Network connectivity problems or invalid API credentials will result in authentication or connection errors.
    • If the specified operation or resource is not found in the bundled API spec, the node throws an error.
  • Error messages:

    • Operation <operationName> not found: Indicates the requested operation does not exist in the API specification. Verify the operation name and resource selection.
    • API errors returned from Crypto APIs (e.g., invalid address format, unauthorized) are passed through and should be handled accordingly.
  • Resolution tips:

    • Ensure all required parameters are correctly set.
    • Confirm that the API key credential is valid and has necessary permissions.
    • Check network connectivity and endpoint availability.

Links and References

Discussion