Changelog: March 2026

What shipped across Jupiter's developer APIs in March 2026. The headline: Ultra and Metis are unified into a single Swap API.
Swap
Swap API V2 is live
The unified Swap API consolidates Ultra and Metis into a single entry point at api.jup.ag/swap/v2, with three endpoints:
GET /order- default path. Returns an assembled transaction with the best price across all routers (Metis, JupiterZ, Dflow, OKX). Includes RTSE, Jupiter Beam, gasless, and RFQ competition. Sign and send to/execute.GET /build- advanced path. Returns raw swap instructions for building custom transactions (add custom instructions, CPI, composability). Metis-only routing, no Jupiter swap fees.POST /execute- managed transaction landing for/ordertransactions.
WTM (what this means) - One API instead of two. Start with /order: it gives the best price because all routers compete, including JupiterZ market makers who often beat onchain routing on major pairs. Only use /build if you need to modify the transaction. Ultra and Metis APIs remain available; new integrations should use the Swap API, and existing integrations are encouraged to migrate when convenient.
Swap API overview · Order & Execute · Build · Migration guides · API Reference
forJitoBundle parameter on the Metis quote endpoint
When set to true, it excludes DEXes that are incompatible with Jito bundles.
WTM - If you submit swaps inside Jito bundles, this guarantees the resulting transaction is bundle-safe instead of failing at submission.
Trigger
Trigger Order API V2 is live
A new authentication model and expanded capabilities:
- Authentication flow - challenge-response auth using wallet signatures instead of API keys
- Vault registration - register a vault to hold funds for trigger orders
- Create and manage orders - create, update, and cancel limit and DCA orders
- Order history - query active and historical orders with filtering
WTM - V2 moves from PDA order accounts to vault-based custody with wallet-signature auth: a leaked JWT can cancel or edit orders but cannot move funds. V1 remains available but is no longer actively maintained; new integrations should use V2.
Lend
Earn earnings endpoint schema changed
The GET /lend/v1/earn/earnings response schema changed:
- Removed:
totalDeposits,totalWithdraws,totalBalance,totalAssetsfields - Changed:
earningstype fromstringtonumber - Added:
slotfield (number) indicating the slot at which earnings were computed
WTM - Update any code that reads the removed fields or parses earnings as a string.
Tokens
Deprecated response fields removed from Tokens V2
Tokens V2 no longer returns the issuer, fees, stats7d, and stats30d response fields. These deprecated fields were removed from the API and the OpenAPI schema.
WTM - Update any code that reads them. For stats, the supported windows are stats5m, stats1h, stats6h, and stats24h.
AI
Jupiter CLI documented
Use Jupiter APIs directly from the command line for swaps, price checks, and token lookups, alongside a reworked AI section focused on trading and building workflows.