Changelog: April 2026
What shipped across Jupiter's developer APIs in April 2026. A big month: the Developer Platform launched, transaction submission went public, and Prediction Markets shipped two breaking changes.
Breaking changes
Prediction Markets: metadata fields moved to the top levelBreaking
All fields previously nested under markets[].metadata moved to the top level of the market object on April 10, 2026. This affects all /events/* and /markets GET endpoints.
| Old path | New path |
|---|---|
markets[].metadata.title | markets[].title |
markets[].metadata.isTeamMarket | markets[].isTeamMarket |
markets[].metadata.rulesPrimary | markets[].rulesPrimary |
markets[].metadata.rulesSecondary | markets[].rulesSecondary |
markets[].metadata.openTime | markets[].openTime |
markets[].metadata.closeTime | markets[].closeTime |
WTM (what this means) - Responses no longer include markets[].metadata. Update your code to read these fields from the top-level market object.
Prediction Markets: minimum order size increased to $5Breaking
The minimum order amount increased from $1 to $5 on April 14, 2026. Orders below $5 are rejected. Ensure all order amounts in your integration are at least $5.
Trigger V2: verify-token endpoint removedBreaking
The /auth/verify-token endpoint is gone from the API and the OpenAPI spec.
WTM - Nothing replaces it; validate your JWT by using it. The challenge and login endpoints are unchanged.
Transaction Submission
/submit is publicly available
POST https://api.jup.ag/tx/v1/submit accepts any signed Solana transaction and lands it through Jupiter's optimised infrastructure, including Jupiter Beam for sub-second landing and MEV protection.
- Requires a minimum tip of 0.001 SOL to one of the supported tip receiver addresses
- Works with any signed Solana transaction, not just Jupiter swaps
WTM (what this means) - Jupiter operates one of the highest-staked validators on Solana, and /submit opens that landing pipeline to any integrator. Run it in parallel with your existing RPC submission and let whichever lands first win.
Swap
RTSE slippage estimation documented
Real-Time Slippage Estimator (RTSE) documentation is now available. RTSE estimates slippage based on current market conditions.
- Automatic with
/order, no configuration needed - Opt-in with
/buildviaslippageBps=rtse
WTM - Fixed slippage is either too tight (failed transactions) or too loose (worse fills). RTSE picks the value per swap from live market data, so you stop hand-tuning it.
Tokens
VRFD Express Verification API
Token projects can verify their tokens on Jupiter programmatically through a three-step flow:
- Check eligibility - confirm the token meets verification requirements
- Craft transaction - build the verification transaction
- Execute verification - submit and complete verification
New Tokens documentation, API reference pages, and a verification OpenAPI spec are available.
stocks tag on /tokens/v2/tag
Query tokenized equities (Ondo, Remora, and others) the same way you query lst or verified.
Platform
Jupiter Developer Platform launched
Portal documentation has been rewritten for the Jupiter Developer Platform launch, covering the full platform experience:
- Setup - creating an account and generating API keys
- Plans - free and paid tiers with rate limits and features
- Rate Limits - per-endpoint limits and how throttling works
- Migration - moving from
lite-api.jup.agtoapi.jup.ag - Responses - standard response formats and error codes
- FAQ - common questions and troubleshooting
Dedicated rate limit buckets for /execute and /submit
Each gets its own bucket, separate from the general API limit and from each other: Keyless 20 RPS, Free 50 RPS, Paid 100 RPS.
WTM - Heavy order-fetching no longer throttles your transaction landing. Budget the two endpoints independently.
JupUSD
JupUSD and JUICED developer documentation
- JupUSD - mint and redeem Jupiter's native stablecoin, with API integration guides
- JUICED - collateral integration documentation for leveraged vault positions