Jupiter Ultra icon

Jupiter Ultra

Jupiter Ultra API operations
Join our community

Actions6

Overview

The "Jupiter Ultra" node integrates with the Jupiter Ultra API to perform various token-related operations on the Solana blockchain ecosystem. Specifically, the Order operation allows users to request a quote and obtain an unsigned swap transaction for exchanging one token (input mint) to another (output mint). This is useful in decentralized finance (DeFi) scenarios where users want to programmatically get swap quotes and prepare transactions for token swaps without immediately executing them.

Practical examples include:

  • Building automated trading bots that fetch swap quotes before deciding to execute.
  • Creating wallet applications that show users potential swap rates and generate unsigned transactions for user approval.
  • Integrating referral programs by specifying referral accounts and fees during order creation.

Properties

Name Meaning
Base URL The base URL of the Jupiter Ultra API endpoint. Defaults to https://lite-api.jup.ag/ultra/v1.
Input Mint The mint address of the input token to swap from (required).
Output Mint The mint address of the output token to swap to (required).
Amount The amount of the input token to swap, specified in the smallest unit (e.g., lamports or atoms) (required).
Taker Optional wallet address of the taker performing the swap.
Referral Account Optional referral account address to credit for the swap.
Referral Fee Referral fee in basis points (0-10000), applicable only if a referral account is provided.
Exclude Routers Comma-separated list of liquidity routers to exclude from routing the swap.

Output

The node outputs a JSON object containing the response from the Jupiter Ultra API's /order endpoint. This typically includes:

  • A quote for the requested token swap.
  • An unsigned transaction payload representing the swap.
  • Additional metadata such as price impact, fees, and route information.

This output can be used downstream to review swap details or to sign and submit the transaction using other nodes or custom logic.

The node does not output binary data.

Dependencies

  • Requires access to the Jupiter Ultra API, which may optionally use an API key credential for authenticated requests.
  • No mandatory credentials are required, but if an API key is provided, it will be sent in the x-api-key header.
  • Network connectivity to the specified Base URL is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing input/output mint addresses will cause the API to reject the request.
    • Incorrect amount format or zero amount may result in errors or empty quotes.
    • Providing invalid referral account or fee values might cause the API to ignore referral parameters or return errors.
    • Network or authentication failures if the API key is invalid or missing when required.

  • Error messages:

    • "Unknown operation": Indicates the selected operation is not supported; ensure "Order" is selected.
    • HTTP errors from the API (e.g., 400 Bad Request) usually indicate malformed parameters.
    • If the node throws an error about missing required parameters, verify all required fields are filled correctly.

  • Resolution tips:

    • Double-check mint addresses and amounts.
    • Ensure optional fields like referral account and fee are consistent.
    • Verify network connectivity and API key validity if used.
    • Use the node’s "Continue On Fail" option to handle errors gracefully during batch processing.

Links and References

Discussion