Changelog: June 2026

Swap API /order supports integrator fees on JupiterZ routes. Requests using referralAccount and referralFee can receive RFQ quotes when JupiterZ is the best eligible route.

WTM (what this means) - Previously, charging integrator fees could cost you RFQ quotes from JupiterZ market makers, which often beat onchain routing on major pairs. You no longer trade fee revenue for price quality. Integrator-sponsored gas remains separate: setting payer to a wallet different from taker still restricts routing to Metis.

Order & Execute · Gasless Swaps

When the output token account does not exist, Jupiter's gas wallet funds it.

WTM - The last SOL requirement on the JupiterZ gasless path is gone; previously JupiterZ was not routed for takers who could not pay ATA rent.

Gasless Swaps

When a router can price the swap but cannot build a transaction, transaction is an empty string and errorCode/errorMessage explain why.

WTM - Handle the empty-transaction case explicitly instead of treating every 200 response as executable. The four error codes are documented in the API reference.

Order & Execute

How Limit Order v2 and JIT Swap are built: monitoring any-token-to-any-token orders at scale, keeping execution correct off-chain, and re-routing trades on-chain at the moment they execute.

The Any-Any Problem · Correctness Under Failure · JIT Swap

Jupiter Forecast is a Solana-native, fully onchain prediction market. The first markets are 15-minute Bitcoin up/down rounds, settled from the Chainlink BTC/USD price. It runs on the Prediction API under the bisonfi provider, and every outcome is a regular token mint.

• Discover live rounds with GET /prediction/v1/events?provider=bisonfi, then build, sign, and submit through /prediction/v1/orders and /execute
• Or trade outcome tokens directly: GET /swap/v2/order from USDC to the market's outcomeMint, then /execute
• USDC-only deposits; the Prediction API path caps orders at 5 to 250 USDC, and winning positions settle automatically with no claim step

WTM - A pioneering new source of prediction markets, native to Solana and fully onchain — and because each position is just a token, you can trade the markets with a regular swap through the Swap API, no prediction-specific integration needed. Use the Prediction API when you want Jupiter to track positions, P&L, and settlement; either way, winners settle automatically with no claim step.

Forecast Docs · Prediction API

Read borrow vaults and user positions, and build collateralised borrow transactions over HTTP.

• GET https://api.jup.ag/lend/v1/borrow/vaults and GET /borrow/positions return vault config and user positions
• POST /borrow/operate and POST /borrow/operate-instructions build a transaction that creates a position, deposits collateral, borrows, repays, and withdraws using signed colAmount and debtAmount

WTM - You can integrate Jupiter Lend borrowing from any language without the TypeScript SDK. A single universal operate endpoint covers the whole position lifecycle.

Borrow API guide · Borrow API reference

Non-JUP currencies are converted to 1000 JUP via Ultra under the hood. Pass paymentCurrency to craft-txn and execute. On non-JUP paths, craft-txn returns the swap input amounts and execute takes a paymentAmount.

WTM - Token projects no longer need to acquire JUP before verifying. Hold any of the four supported currencies and the API handles the conversion.

Express Verification API

The Content API is being phased out in favour of a more comprehensive replacement as part of an upcoming Tokens API update. No sunset date yet.

WTM - Plan your migration off the Content API endpoints; watch this changelog for the replacement announcement.

Organisations and teams, API keys and permissions, the firewall, request logs, analytics, and account security are now documented.

WTM - Team accounts with scoped key permissions, a firewall to restrict where and how keys are used, and request logs and analytics to see what your keys are doing.

Platform Features

Back in April we put up a bounty to find out where our APIs suck: build something with them, then tell us everything wrong with the developer experience — confusing documentation, bad error messages, whatever slowed you down. 258 developers did, and their DX reports became our roadmap for fixing devex.

• Winners: Jorge Sierra (@GeekLad), Mike Timashov (@heymike777), Timothy Popoola (@winsznx)
• Best DX reports: @dukedotsol, @legalalien0x, @web3_theo
• 3,000 JupUSD prize pool across six winners

Winners announcement