Jupiter Token icon

Jupiter Token

Jupiter Token API v2 operations

Actions4

Overview

The "Jupiter Token" node integrates with the Jupiter Token API v2 to retrieve token information on the Solana blockchain. 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 with first pools.

This node is useful for workflows that require up-to-date token metadata or want to filter tokens based on specific criteria like tags or trading activity. For example, a user can search for tokens matching "USDC" or a specific mint address, get all verified tokens, or fetch top trending tokens in the last 24 hours.

Properties

Name Meaning
Base URL The base URL of the Jupiter Token API v2 endpoint. Default: https://lite-api.jup.ag/tokens/v2
Operation The action to perform. Options:
- Search: Search tokens by symbol, name, or mint address
- Get by Tag: Get tokens filtered by a tag (LST or Verified)
- Get by Category: Get tokens by category and time interval
- Get Recent: Get tokens with recently created first pool
Search Query (For Search operation) Search string by symbol, name, or mint address. Multiple mint addresses can be comma-separated (max 100). Example: "USDC, So11111111111111111111111111111111111111112"
Limit (For Search operation) Maximum number of results to return. Minimum value is 1. Default is 50.
Tag (For Get by Tag operation) Token tag filter. Options: lst (Liquid Staking Tokens), verified
Category (For Get by Category operation) Category to get tokens from. Options: toporganicscore, toptraded, toptrending
Time Interval (For Get by Category operation) Time interval for category data. Options: 5m, 1h, 6h, 24h

Output

The node outputs an array of JSON objects corresponding to the tokens retrieved from the API. Each item contains the raw JSON response from the Jupiter Token API for the selected operation.

  • The output field json holds the full API response data.
  • No binary data output is produced by this node.

Example output structure (simplified):

[
  {
    "json": {
      "tokens": [
        {
          "symbol": "USDC",
          "name": "USD Coin",
          "mintAddress": "So11111111111111111111111111111111111111112",
          ...
        },
        ...
      ]
    }
  }
]

Dependencies

  • Requires access to the Jupiter Token API v2 endpoint (default: https://lite-api.jup.ag/tokens/v2).
  • Optionally uses an API key credential for authentication by setting an HTTP header x-api-key.
  • No other external dependencies.

Troubleshooting

  • Common issues:

    • Invalid or empty search query may return no results.
    • Exceeding the maximum allowed mint addresses (more than 100) in the search query could cause errors.
    • Network connectivity issues or incorrect Base URL will result in request failures.
    • Using an unsupported operation value will throw an error.

  • Error messages:

    • Unknown operation: <operation>: Occurs if the operation parameter is not one of the supported options. Fix by selecting a valid operation.
    • HTTP request errors: May indicate network problems or invalid API key. Verify credentials and endpoint accessibility.
    • API rate limits or quota exceeded errors: If using an API key, ensure it has sufficient quota.

  • To handle errors gracefully, enable "Continue On Fail" in the node settings to receive error details per item instead of stopping execution.

Links and References

Discussion