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 information about tokens on the Solana blockchain. It supports multiple operations such as searching tokens by symbol, name, or mint address; filtering tokens by tags; fetching tokens by category and time interval; and getting recently created tokens with their first pool.

This node is useful for workflows that require up-to-date token data from the Solana ecosystem, such as portfolio trackers, token analytics dashboards, or DeFi applications that need to filter or search tokens dynamically.

Example use cases:

  • Searching for a specific token by its symbol or mint address.
  • Retrieving all verified tokens or liquid staking tokens (LST).
  • Getting top trending or top traded tokens within a specified time frame.
  • Fetching the most recently created tokens to monitor new market entries.

Properties

Name Meaning
Base URL Base URL for Jupiter Token API v2. Default is https://lite-api.jup.ag/tokens/v2.
Operation The action to perform. Options: Search, Get by Tag, Get by Category, Get Recent.

Additional properties depending on the selected operation:

Name Meaning
Search Query (For Search operation) Search tokens by symbol, name, or mint address. Multiple mint addresses can be comma-separated (max 100).
Limit (For Search operation) Maximum number of results to return. Minimum value is 1.
Tag (For Get by Tag operation) Filter tokens by tag. Options: LST (Liquid Staking Tokens), Verified.
Category (For Get by Category operation) Category to get tokens from. Options: Top Organic Score, Top Traded, Top Trending.
Time Interval (For Get by Category operation) Time interval for category data. Options: 5 Minutes, 1 Hour, 6 Hours, 24 Hours.

Output

The node outputs an array of JSON objects corresponding to the API response for each input item processed. Each output item contains the full JSON response from the Jupiter Token API for the requested operation.

  • The structure of the JSON depends on the operation and the API endpoint called.
  • If the API returns binary data (not indicated in this code), it would be included accordingly, but this node only handles JSON responses.

Dependencies

  • Requires access to the Jupiter Token API v2 via HTTP GET requests.
  • Optionally uses an API key credential for authentication, which should be configured in n8n credentials and passed as an x-api-key header if available.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing API key may result in authorization errors.
    • Incorrect Base URL or network connectivity issues will cause request failures.
    • Using unsupported operations or invalid parameters will throw errors.

  • Error messages:

    • "Unknown operation: <operation>": Indicates an unsupported operation was selected. Verify the operation property.
    • HTTP request errors: May occur due to network issues or invalid API responses. Check API availability and credentials.
    • If continueOnFail is enabled, errors for individual items will be returned in the output JSON under an error field instead of stopping execution.

Links and References

Discussion