Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to list confirmed transactions by a Kaspa address on a specified network. It is useful for blockchain developers, analysts, or enthusiasts who want to retrieve transaction history related to a particular Kaspa wallet address. For example, you can use this node to monitor incoming and outgoing transactions of a Kaspa address, audit wallet activity, or integrate transaction data into dashboards or automated workflows.

Properties

Name Meaning
network The blockchain network to query (e.g., mainnet, testnet).
address The Kaspa wallet address for which to list confirmed transactions.
context Optional context string to correlate responses with requests (for tracking purposes).
limit Optional number to limit the number of returned transactions.
startingAfter Optional cursor string to paginate results, specifying the starting point after a given transaction ID.

Output

The node outputs an array of JSON objects representing confirmed transactions associated with the specified Kaspa address. Each object contains detailed transaction data as returned by the Crypto APIs service, such as transaction IDs, timestamps, amounts, confirmations, and other relevant blockchain metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Requires 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 dynamically resolve API paths and parameters.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Providing an incorrect or malformed Kaspa address may result in errors or empty results.
    • Network parameter must match supported networks; otherwise, the API may reject the request.
    • Pagination parameters (limit, startingAfter) must be valid to avoid unexpected results.
  • Error messages:

    • "Operation <operationName> not found" indicates the requested operation is not defined in the API spec or was misspelled.
    • API response errors typically include descriptive messages from Crypto APIs; check the error details for guidance.
    • If the node throws errors about missing required parameters, ensure all mandatory fields (network, address) are provided.
  • Resolution tips:

    • Verify API credentials and permissions.
    • Double-check input values for correctness and completeness.
    • Use the context property to trace and debug requests if supported by your API plan.

Links and References

Discussion