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 cryptocurrency transaction on the Kaspa network by its transaction ID. It is useful for users who want to fetch and analyze transaction details such as status, inputs, outputs, fees, and other metadata related to a Kaspa blockchain transaction.

Practical examples include:

  • Monitoring the status of a Kaspa transaction after broadcasting it.
  • Fetching transaction details for auditing or reporting purposes.
  • Integrating transaction data into dashboards or automated workflows.

Properties

Name Meaning
network The Kaspa network to query (e.g., mainnet, testnet).
transactionId The unique identifier (hash) of the Kaspa transaction to retrieve details for.
context Optional context string to correlate responses with requests (useful for tracking).

Output

The node outputs a JSON array where each item contains detailed information about the requested Kaspa transaction. The structure typically includes fields such as transaction hash, block details, inputs, outputs, confirmations, fees, timestamps, and other relevant blockchain metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Crypto APIs service via an API key credential configured in n8n.
  • The node reads from a local OpenAPI specification file (2024-12-12-final.json) to dynamically build request parameters and paths.
  • Network connectivity to the Crypto APIs endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing transactionId will result in errors or empty responses.
    • Incorrect network value may cause the API to reject the request or return no data.
    • Network connectivity problems can lead to timeouts or failed requests.

  • Error messages:

    • "Operation <operationName> not found": Indicates the internal operation mapping failed; usually a configuration or version mismatch issue.
    • API errors returned from Crypto APIs (e.g., "Transaction not found") should be handled by verifying input parameters.

  • Resolutions:

    • Double-check that the transactionId is correct and corresponds to the specified network.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Verify network connectivity and Crypto APIs service status.

Links and References

Discussion