Jupiter Ultra

Overview

The Jupiter Ultra node provides access to various operations of the Jupiter Ultra API, a service related to token swaps and liquidity on Solana. The node supports multiple operations such as searching tokens, getting token balances, creating swap orders, executing signed transactions, retrieving available liquidity routers, and fetching token risk warnings.

The Search operation specifically allows users to search for tokens by symbol, name, or mint address. This is useful when you want to find tokens matching a query string, for example, searching for "USDC" to get details about the USD Coin token or other tokens with similar names or symbols.

Practical examples:

• Quickly find token information before performing swaps.
• Filter tokens by partial names or symbols in automated workflows.
• Use token search results to dynamically populate dropdowns or inputs in subsequent nodes.

Properties

Output

The output is an array of JSON objects representing the response from the Jupiter Ultra API's search endpoint. Each item corresponds to one input item processed.

• The json field contains the parsed JSON response from the API, which includes token data matching the search query.
• The exact structure depends on the API response but typically includes token metadata such as symbol, name, mint address, decimals, and possibly other attributes.
• No binary data output is produced by this operation.

Example output snippet (conceptual):

{
  "json": {
    "tokens": [
      {
        "symbol": "USDC",
        "name": "USD Coin",
        "mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
        "decimals": 6
      },
      ...
    ]
  }
}

Dependencies

• Requires access to the Jupiter Ultra API endpoint specified by the Base URL.
• Optionally uses an API key credential if provided; the key is sent in the x-api-key header.
• No mandatory credentials are required for the search operation, but providing an API key may improve rate limits or access.
• Network connectivity to the API endpoint is necessary.

Troubleshooting

• Common issues:

  • Incorrect Base URL leading to connection errors.
  • Invalid or missing API key causing authorization failures if the API requires it.
  • Empty or malformed search queries returning no results or errors.

• Error messages:

  • "Unknown operation": Occurs if an unsupported operation is selected; ensure "Search" is chosen.
  • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or endpoint issues.
  • Network timeouts or DNS resolution failures suggest connectivity problems.

• Resolutions:

  • Verify the Base URL is correct and reachable.
  • Provide a valid API key credential if required by your API plan.
  • Ensure the search query is properly formatted and not empty if you expect results.
  • Check network settings and firewall rules allowing outbound requests.

Links and References

• Jupiter Ultra API Documentation (general reference for API endpoints and parameters)
• Solana Token Program (background on token mints and standards)

This summary focuses on the Search operation of the Jupiter Ultra node as requested.