Practical overview
When it fits
Use it when building a Rust service or application that needs programmatic access to Jupiter API requests and order execution.
Who it is for
- Rust developers integrating Jupiter quotes, orders, or swap execution into an application.
- Teams building backend token and price lookup, trigger-order, or recurring-order integrations.
Documented uses
- Request a quote or order for a token pair and amount.
- Retrieve an unsigned Ultra transaction, sign it in an application, and submit it to Jupiter.
- Integrate the SDK's stated Swap, Trigger, Recurring, Token, and Price API coverage.
Requirements & limits
The source repository is public and lists an MIT license. Installation is documented through Cargo.
- The library covers Ultra, Swap, Trigger, Recurring, Token, and Price APIs, according to its README.
- Composable builders include request options for taker, referral, fee, and excluded routers.
- The demonstrated Ultra flow requires the integrating application to sign the transaction before submitting it for execution.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Request and submit a Jupiter Ultra order
Use the SDK example flow to request an Ultra order and submit its signed transaction.
Before you start
- A Rust application with the jup-ag-sdk dependency.
- Input and output token identifiers, an amount, and a taker wallet address.
- An application-side method for signing the returned transaction.
Steps
Initialize JupiterClient with the Lite API endpoint.
Build an UltraOrderRequest with the input token, output token, amount, and taker address.
Call get_ultra_order and obtain the unsigned transaction and request ID.
Sign the transaction in the application, then submit it with UltraExecuteOrderRequest through ultra_execute_order.
Expected outcome
The SDK submits the signed order to Jupiter and the example reads a transaction signature from the execution response.
Guide limitations
- The example leaves transaction signing as an application-side step.
- The README example contains an apparent variable-name inconsistency between the order response and the request ID reference; consult the linked examples before adapting it.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- Jupiter-DevRel/jup-rust-sdk · Official homepage title · retained in its source language