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; fetching tokens by specific tags; retrieving tokens by category and time interval; and getting recently created tokens.

The Get by Tag operation specifically fetches tokens filtered by a predefined tag, such as "LST (Liquid Staking Tokens)" or "Verified" tokens. This is useful when you want to quickly obtain lists of tokens that belong to certain classifications without manually filtering them yourself.

Practical examples:

  • Fetching all verified tokens to display trustworthy assets in a portfolio.
  • Retrieving liquid staking tokens to analyze staking-related assets.
  • Integrating token data into dashboards or DeFi applications that require categorized token lists.

Properties

Name Meaning
Base URL The base endpoint URL for the Jupiter Token API v2. Defaults to https://lite-api.jup.ag/tokens/v2.
Tag The token tag to filter by. Options are:
- LST (Liquid Staking Tokens)
- Verified

Output

The node outputs an array of JSON objects representing the tokens retrieved from the Jupiter Token API based on the selected tag. Each item corresponds to one token's data as returned by the API.

The exact structure of each token object depends on the API response but typically includes details like token symbol, name, mint address, and other metadata relevant to the token.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Jupiter Token API v2 via HTTP GET requests.
  • Optionally uses an API key credential if provided, sent as an x-api-key header for authenticated requests.
  • No additional environment variables or configurations are strictly required beyond the optional API key credential.

Troubleshooting

  • Common issues:

    • Incorrect or unreachable Base URL may cause request failures.
    • Using an invalid or expired API key (if set) can result in authentication errors.
    • Selecting an unsupported tag value will cause the node to throw an error.

  • Error messages:

    • "Unknown operation: <operation>": Indicates an invalid operation parameter was passed. Ensure the operation is set to "tag" for this use case.
    • HTTP request errors: Network issues or API downtime may cause failures. Verify network connectivity and API status.
    • If the node is configured to continue on fail, errors will be returned in the output JSON under an error field for each failed item.

Links and References

Discussion