Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Transactions By Address Solana" under the resource "addresses-latest" interacts with a cryptocurrency API to retrieve a list of transactions associated with a specific Solana blockchain address. It is useful for users who want to track or analyze transaction history on the Solana network for a given wallet address.

Common scenarios include:

  • Monitoring incoming and outgoing transactions for a Solana wallet.
  • Auditing transaction activity for compliance or record-keeping.
  • Building dashboards or reports that display recent transaction data by address.

Practical example: A user inputs a Solana wallet address and selects the Solana network; the node returns a list of recent transactions involving that address, which can then be processed or displayed downstream in an n8n workflow.

Properties

Name Meaning
network The blockchain network to query (e.g., Solana mainnet or testnet).
address The Solana wallet address whose transactions are to be listed.
context Optional context string to correlate requests or responses (usage depends on API).
limit Optional limit on the number of transactions to return.
startingAfter Optional pagination token to start listing transactions after a specific point.

Output

The output is a JSON array where each element represents a transaction related to the specified Solana address. Each transaction object contains details as provided by the underlying Crypto APIs service, such as transaction identifiers, timestamps, amounts, and other relevant metadata.

If the API supports binary data (not indicated here), it would typically represent raw transaction data or related files, but this operation focuses on JSON transaction listings.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs an API key credential configured in n8n for authentication.
  • The node reads from a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to map operations and parameters.
  • No additional external dependencies beyond the Crypto APIs service and standard n8n environment.

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 Address or Network: Providing an incorrect or unsupported Solana address or network may result in API errors or empty results. Verify the address format and network selection.
  • API Rate Limits or Authentication Errors: Ensure the API key credential is valid and has sufficient permissions. Check for rate limiting if many requests are made in a short time.
  • Pagination Issues: Using startingAfter incorrectly may cause missing or repeated transactions. Use tokens returned from previous calls properly.

Links and References

Discussion