Crowd TT Explorer icon

Crowd TT Explorer

Interact with TT API

Overview

This node, named "Crowd TT Explorer," interacts with the TT API to retrieve token trade data associated with a specific wallet address. The primary operation supported is "Get Wallet Token Trades," which fetches paginated token trade records for a given stake wallet address.

Typical use cases include:

  • Monitoring token trading activity of a particular wallet.
  • Analyzing transaction history for auditing or reporting purposes.
  • Integrating wallet trade data into broader blockchain analytics workflows.

For example, a user can input a Cardano stake wallet address and retrieve recent token trades made by that wallet, specifying pagination parameters to control the volume of returned data.

Properties

Name Meaning
Wallet Address The stake wallet address to query (e.g., a Cardano stake address starting with "stake1...")
Page Page number for pagination; controls which page of results to retrieve
Per Page Number of results per page; controls how many trade records are returned per request
Unit Optional unit parameter to filter or specify the type of token unit

Output

The node outputs an array of JSON objects, each representing the response from the TT API for the requested wallet token trades. Each output item corresponds to one input item and contains the full JSON response from the API under the json property.

The structure of the JSON response depends on the TT API but generally includes details about token trades such as trade IDs, timestamps, token identifiers, amounts, prices, and other relevant trade metadata.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the TT API.
  • The node makes HTTP GET requests to the endpoint:
    https://openapi.taptools.io/api/v1/wallet/trades/tokens
  • The API key must be configured in n8n credentials before using this node.

Troubleshooting

  • Common issues:

    • Invalid or missing wallet address format may cause the API to return errors or empty results.
    • Pagination parameters (Page, Per Page) set to invalid values (e.g., negative numbers) might lead to unexpected responses.
    • Missing or incorrect API key will result in authentication failures.

  • Error messages:

    • If the API returns an error, it will be captured and returned in the output JSON under an error field if "Continue On Fail" is enabled.
    • Without "Continue On Fail," errors throw a node operation error indicating the failure reason.

  • Resolution tips:

    • Verify the wallet address format matches expected patterns.
    • Ensure the API key credential is correctly set up and valid.
    • Adjust pagination parameters to reasonable values.
    • Enable "Continue On Fail" during testing to capture error details without stopping workflow execution.

Links and References

Discussion