Jupiter Ultra: /order plus /execute, plus Trigger logoJupiter Ultra: /order plus /execute, plus Trigger
Get an order, sign it, execute it. Jupiter lands the tx. Trigger V2 is the limit and DCA vault on the same key.
devrels.xyz/a/269Jupiter Ultra is the hosted swap path: Jupiter quotes, you sign, Jupiter lands. On the current docs that is Swap API V2 Meta-Aggregator. Base URL https://api.jup.ag/swap/v2. Same /order plus /execute shape as the old ultra-api host, new base.
Trigger V2 sits next to it. Limit, take-profit, stop-loss, OCO, and DCA share one vault. Price orders fire on a USD condition. DCA splits a deposit on a schedule. Orders stay off-chain until they execute.
Which endpoint
| Path | Job |
|---|---|
GET /swap/v2/order then POST /swap/v2/execute | Meta-Aggregator. Best price, managed landing, platform fee. Start here. |
GET /swap/v2/build | Metis instructions only. CPI, extra ix, your RPC or tx.jup.ag with a SOL tip. |
POST /trigger/v2/orders/price and /orders/dca | Vault orders. JWT plus API key. USD triggers, partial fills, edit in place. |
Self-host Metis is a different product. See Metis binary. Engine map: aggregators for developers.
Swap happy path
Keyless api.jup.ag is 0.5 RPS. Production: portal key in x-api-key. Free tier is 1 RPS. requestId from order goes to execute with the signed transaction.
curl -s "https://api.jup.ag/swap/v2/order?inputMint=So11111111111111111111111111111111111111112&outputMint=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v&amount=100000000&taker=YOUR_PUBKEY" \
-H "x-api-key: $JUPITER_API_KEY"Response includes base64 transaction, requestId, router (metis, jupiterz, dflow, okx), and mode (ultra or manual). Sign, then POST execute. Jupiter retries landing. RTSE slippage is applied at order time.
Trigger V2
Auth is challenge-response JWT plus the same API key. Deposits go to a Privy vault, not a public PDA. Trigger V1 still runs; new work is V2. Recurring V1 DCA is unmaintained. Migrate to /trigger/v2/orders/dca. Minimums in the live docs (about 10 USD per DCA round, two or more rounds).
Docs: Order and Execute · Trigger · Ultra to Meta-Aggregator. Portal: developers.jup.ag/portal.
People and links
| Who / what | Where |
|---|---|
| Docs | developers.jup.ag/docs |
| X | @JupiterExchange |
| Related | Metis self-host · Aggregators |
Keep reading
Same-chain stays Jupiter-class. Cross-ecosystem needs routers/solvers + messaging + honest status. Pyth prices the edge cases; Wormhole moves messages/assets.
Not every “swap API” is the same product. Here is what each aggregator layer actually gives your app — routing engines, landing, fees, AI tooling, and when to call whom.
Self-hosted Metis router binary — github.com/jup-ag/metis-binary, metis.builders docs, BINARY_KEY + RPC + optional Yellowstone, local :8080 quote/swap.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
