Jupiter Token icon

Jupiter Token

Jupiter Token API v2 operations
Join our community

Actions4

Overview

The "Jupiter Token" node interacts with the Jupiter Token API v2 to retrieve token data based on different criteria. It supports multiple operations such as searching tokens by symbol, name, or mint address; fetching tokens by tag; retrieving tokens by category and time interval; and getting recently created tokens.

For the Get by Category operation specifically, the node fetches tokens belonging to a selected category (e.g., Top Organic Score, Top Traded, Top Trending) within a specified time interval (e.g., 5 minutes, 1 hour, 6 hours, 24 hours). This is useful for users who want to analyze or monitor token performance trends over various periods.

Practical examples:

  • A trader wants to get the top trending tokens in the last 24 hours to identify potential investment opportunities.
  • An analyst needs to review tokens with the highest organic score over the past 6 hours to understand market sentiment.
  • A developer building a dashboard displays tokens categorized by trading volume in the last hour.

Properties

Name Meaning
Base URL The base endpoint URL for the Jupiter Token API v2. Defaults to https://lite-api.jup.ag/tokens/v2.
Category The category of tokens to retrieve. Options: Top Organic Score, Top Traded, Top Trending.
Time Interval The time range for which to fetch category data. Options: 5 Minutes, 1 Hour, 6 Hours, 24 Hours.

Output

The node outputs an array of JSON objects representing the tokens retrieved from the Jupiter Token API according to the selected category and time interval.

  • The json field contains the raw response from the API, which typically includes token details such as symbol, name, scores, trading volumes, and other relevant metrics depending on the category.
  • Each output item is paired with its input item index (pairedItem) for traceability.
  • The node does not output binary data.

Dependencies

  • Requires access to the Jupiter Token API v2 endpoint.
  • Optionally uses an API key credential for authentication if provided; this key is sent via the x-api-key HTTP header.
  • No additional environment variables or configurations are strictly required beyond the optional API key credential.

Troubleshooting

  • Common issues:

    • Incorrect Base URL may lead to connection errors or invalid responses.
    • Selecting an unsupported category or interval will cause the node to throw an error.
    • Missing or invalid API key might result in authorization failures or limited access.

  • Error messages:

    • "Unknown operation: <operation>": Indicates that the specified operation is not recognized by the node. Verify the operation parameter.
    • HTTP request errors (timeouts, 4xx/5xx responses): Check network connectivity, API availability, and credentials.
    • If the node is set to continue on fail, errors will be returned in the output JSON under an error property for each failed item.

Links and References

Discussion