The Swap API unifies Jupiter’s swap capabilities into a single entry point atDocumentation Index
Fetch the complete documentation index at: https://dev.jup.ag/docs/llms.txt
Use this file to discover all available pages before exploring further.
https://api.jup.ag/swap/v2. Two paths cover every use case:
- Meta-Aggregator: all routing engines compete for the best price. You get a fully assembled transaction, sign it, and Jupiter handles landing.
- Router: Metis onchain routing only. You get raw swap instructions with full transaction control for custom builds, CPI, and composability.
Meta-Aggregator
All routers compete (Metis, JupiterZ, Dflow, OKX). Best price, simplest flow. Sign and send to Jupiter for managed landing.
Router
Metis onchain routing. Get raw swap instructions to build your own transaction. Add custom instructions, CPI, or modify the transaction however you need.
Choosing a path
| Meta-Aggregator | Router | |
|---|---|---|
| Endpoints | /order + /execute | /build + /submit |
| Returns | Assembled transaction | Raw swap instructions |
| Routers | All (Metis, JupiterZ, Dflow, OKX) | Metis only |
| Best for | Most integrations. Best price, simplest flow. | Custom transactions, CPI, composability. |
| Transaction landing | Managed via /execute (optimised slippage, priority fees, proprietary landing pipeline) | Self-managed via your own RPC, or via /submit with SOL tips for Jupiter’s proprietary landing pipeline |
| Swap fees | Yes (Jupiter platform fee) | No |
| Integrator fees | Referral fees (referralAccount + referralFee) | Platform fee only (platformFeeBps) or DIY |
| Gasless | Automatic gasless, or your own payer | Use your own payer |
| Transaction modification | No | Full control |
Routing engines
Jupiter’s routing combines multiple engines and selects the best execution price across all of them, with a self-learning mechanism that automatically sidelines underperforming sources.| Engine | Role | Availability |
|---|---|---|
| Metis | Jupiter’s onchain routing engine. Multi-hop, multi-split swaps across Solana DEXes. Also available as an independent public good. | Meta-Aggregator + Router |
| JupiterZ | RFQ (Request for Quote) system where market makers compete to provide off-chain liquidity. Often beats onchain by 5-20bps on major pairs. | Meta-Aggregator only |
| Dflow | Third-party on-chain router. | Meta-Aggregator only |
| OKX | Third-party OKX liquidity. | Meta-Aggregator only |
JupiterZ (RFQ) is only available through the Meta-Aggregator.
- Jupiter runs safety and validation mechanisms between integrators and market makers, and market makers have last-look execution rights, which requires controlled transaction handling to ensure validity and prevent spam.
- Transactions routed through JupiterZ cannot be modified after
/orderreturns them, so use cases that require CPI, custom instructions, or any transaction modification must use the Router path.
Endpoints
All endpoints require an API key via thex-api-key header. Get one at Portal.
Meta-Aggregator
| Method | Endpoint | Description |
|---|---|---|
| GET | /swap/v2/order | Get a quote and assembled transaction |
| POST | /swap/v2/execute | Execute a signed /order transaction with managed landing |
| Method | Endpoint | Description |
|---|---|---|
| GET | /swap/v2/build | Get a quote and raw swap instructions |
| POST | /tx/v1/submit | Submit any signed transaction through Jupiter’s proprietary landing pipeline with SOL tips |
Learn More
Advanced
Gasless swaps, compute unit estimation, reducing transaction size and latency.
Migration Guides
Migrating from Ultra or Metis to the Swap API.
Integrate into routing
If you want your liquidity routed through Jupiter:- DEX operators: Integrate DEX into Metis to get your markets included in Jupiter’s onchain routing.
- Market makers: Integrate into JupiterZ (RFQ) to provide off-chain liquidity via the RFQ system.