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 specific Solana blockchain transaction by its transaction hash (signature). It is useful for users who want to fetch comprehensive data on a particular transaction on the Solana network, such as developers monitoring transaction statuses, auditors verifying transaction details, or analysts gathering blockchain data.

A practical example would be: given a Solana transaction signature, the node fetches all associated details like confirmations, involved addresses, amounts, and status, enabling further processing or reporting within an n8n workflow.

Properties

Name Meaning
network The Solana network to query. This could be mainnet, testnet, or other supported networks.
signature The unique transaction hash (signature) identifying the Solana transaction to retrieve.
context Optional context string to correlate or label the request; usage depends on API support.

Output

The node outputs JSON data representing the full details of the specified Solana transaction. This includes all metadata returned by the Crypto APIs endpoint for that transaction, such as block confirmations, transaction status, involved parties, amounts, fees, and timestamps.

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 from a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to resolve API paths and parameters.
  • Uses internal helper functions to perform HTTP requests to the Crypto APIs service.

Troubleshooting

  • Common issues:

    • Invalid or missing transaction signature will cause the API call to fail.
    • Incorrect network parameter may lead to no results or errors if the transaction does not exist on the specified network.
    • Missing or invalid API authentication token will result in authorization errors.
  • Error messages:

    • Operation <operationName> not found: Indicates the requested operation is not defined in the API spec or the node configuration; ensure correct operation selection.
    • API errors returned from Crypto APIs (e.g., 404 Not Found, 401 Unauthorized) will be surfaced as node errors.
  • Resolutions:

    • Verify the transaction signature is correct and exists on the chosen network.
    • Confirm the network parameter matches the intended Solana environment.
    • Ensure the API key credential is properly set up and has necessary permissions.
    • Use "Continue On Fail" option in the node settings to handle errors gracefully in workflows.

Links and References

Discussion