New Legacy Swap API Parameter: nativeDestinationAccount

Send native SOL directly to any account post swap.

---

What it does:
* Pass in a public key of an account to receive native SOL from the swap output.
* This is similar to destinationTokenAccount, but instead of receiving WSOL in a token account, you receive native SOL in a regular account.

For full details, check the API reference:
https://dev.jup.ag/api-reference/swap/swap#body-native-destination-account

---

NPM Package:
The npm package with the latest schema has been published: https://www.npmjs.com/package/@jup-ag/api/v/6.0.46

We just published an important update on Metis v7 and its transition to an independent public good under https://metis.builders:

https://x.com/jupiterexchange/status/1990479870502031424?s=46

Key changes:
- Metis v7 moves to an authenticated access for the Binary
- Integrators have 1 month to migrate to the new v7 Binary; older versions will stop working after the window
- Metis v7 includes new routing upgrades, expanded liquidity integrations, and engine-level improvements

Important:
If you are using Metis Binary or Metis in any form of interface, it should be labeled as Metis and not Jupiter.

For Binary access, teams can request a key at https://portal.metis.builders (requires staked JUP to prevent spam).

Please read the full post and share your feedback - this is an important transition for current Metis integrators.

Search Endpoints Update:
We'll be deprecating the experimental data: ctLikes and smartCtLikes response field in the search endpoints.

- This will take effect this week and it affects both search endpoints in Ultra API and Tokens API.
- If you are using the field for any purpose, please move off and stop using it.

Legacy Swap API Update:
1. The routePlan[].percent field in the Legacy Swap API quote response may return null.

- Please update to handle null values for this field.
- This change will affect when using instructionVersion=V2 only and has taken effect.

2. Reminder, we are deprecating feeAmount and feeMint in each routePlan.

- Note that the outAmount already factors in these fees taken by the AMM.
- To ensure smooth migration, we will show 0 for feeAmount and the input mint as the feeMint. Then, slowly, we will deprecate them.
- This does not relate to additional integrator fees.

⚠️ Lite API Deprecation

lite-api.jup.ag will be deprecated on 31 December 2025.

This change is to help us provide a better end-to-end developer experience moving forward:
1. Observability for us and importantly metrics/logs for you in Portal (coming soon!)
2. Prevent further spam and aid in maintainability

• Migrate to api.jup.ag and use with an API key
• API key is free to generate
• Free tier remains at 60 req/min
• Paths unchanged, only base URL changes
• No action required for Pro/paid tier

Get key: https://portal.jup.ag
Migration guide: https://dev.jup.ag/portal/migrate-from-lite-api

If you need more help or have questions, please reach out to us in Discord

We are aware that Cloudflare is down, and some of our services are affected, we are looking at possible solutions

(Cloudflare has resolved the issue)

Update on Lite API Deprecation

We've heard your feedback.

- Lite API will remain active until 31st January 2026.
- Allowing more time for migration.
- While we finalize a plan around future pricing plan and rate limit strategy for different use cases.

⚠️ Action Required: Metis Binary v7 Migration

We're deprecating all Metis versions prior to v7.0.0 on February 10, 2026.

What this means
If you're running a self-hosted API on pre-v7 versions, it will stop working after this date.

Pre-v7 users
- Upgrade to latest versions (at least v7+)
- https://github.com/jup-ag/metis-binary/releases

Binary Key
- Ensure a binary key is used to access the binary
- Request yours at https://portal.metis.builders

More info from prev announcements
- https://t.me/jup_dev/140
- https://x.com/JupiterExchange/status/1990479884246761788

For questions regarding the binary, please discuss here: https://t.me/+HBVrLVB6BV9hMGY1

📢 Update on Lite API Deprecation

We’ve been gathering early feedback from some teams using Jupiter APIs and need more time to finalize a pricing and rate-limit structure that works across different use cases.

To avoid forcing premature migrations, we’ve decided to extend the Lite API availability for a few more months.

We’re actively evaluating feedback to land on a clearer long-term structure. Thanks for the feedback so far. If you have questions or want to share input, please reach out to us (@0xYankee or @anmoldotsol).

We’ll share clear timelines and details around deprecation and the new pricing model soon, once decisions are finalized.

🚨 FINAL REMINDER: Metis Binary v7 Migration — Deadline Feb 16

The deprecation of Metis versions prior to v7.0.0 is now in effect. The final cutoff is February 16, 2026 — after this date, pre-v7 binary will stop working.

Upgrade now
• Update to v7+ at minimum
• https://github.com/jup-ag/metis-binary/releases

Binary Key
• Ensure you have a binary key to access the binary
• Request yours at https://portal.metis.builders

Previous announcements
• https://t.me/jup_dev/145
• https://t.me/jup_dev/140
• https://x.com/JupiterExchange/status/1990479884246761788

For questions regarding the binary, please discuss here: https://t.me/+HBVrLVB6BV9hMGY1

Heads up, Pumpfun has released a breaking change

• We are looking into what's needed to be done
• At time of writing, most if not all Pumpfun related swaps will face the 6023 overflow error

https://t.me/pump_tech_updates/36

===

We are actively working on the issue and will share any updates as soon as possible.

Update on the above, we've deployed the fix to all regions, please check and reach out to us if you face any issues.

⚠️ Prediction Market API: Scheduled Maintenance

Wednesday, March 11
7:00-7:45 AM UTC

Trading will be paused for ~30-45 mins.
• API to create/modify orders will return 4XX.
• Orders onchain will not execute or fill.
• No action needed from integrators.

After maintenance, new optional fields available:
• Gasless order support
• Integrator fees

Reminder on the scheduled maintenance on the Prediction Market API

🚨 Pre-v7 Metis Binary — Deprecated & No Longer Functional

Access to older versions of the Metis Binary has been deprecated. If you are using pre-v7 binary, it will no longer work.

Upgrade now
- Update to v7+ at minimum
- https://github.com/jup-ag/metis-binary/releases

Binary Key
- Ensure you have a binary key to access the binary
- Request yours at https://portal.metis.builders

Previous announcements
- https://t.me/jup_dev/147
- https://t.me/jup_dev/145
- https://t.me/jup_dev/140
- https://x.com/JupDevRel/status/2036392094164721981

For questions regarding the binary, please discuss here: https://t.me/+HBVrLVB6BV9hMGY1

📢 Scheduled Maintenance: Jupiter Portal → Developer Platform

We're upgrading Jupiter Portal to the new Jupiter Developer Platform on Monday, April 6th.

Starting this weekend (Apr 4–5):
• API key generation will be temporarily disabled
• Portal payments will be restricted
• Existing API keys and requests continue to work normally
• If your key expires this weekend, it will be extended

On Monday:
• All accounts will be migrated to the new Developer Platform
• Brief interruptions to the portal dashboard may occur
• API requests via api.jup.ag might be affected momentarily (~1-5 mins).
• Lite API requests via lite-api.jup.ag will NOT be affected.

What stays the same:
• Your API keys are preserved
• Same base URL: api.jup.ag - no endpoint changes
• All existing users get a 3-month grace period at your current rate limits

⚠️ After migration, API keys cannot be fully viewed. Make sure you have your existing keys saved before Monday.

📖 Migration guide: https://dev.jup.ag/docs/portal/migration

Update on the scheduled maintenance:

We have fully migrated to the new Developer Platform!

Sign in at https://developers.jup.ag to:
• View your migrated API keys in your legacy organisation
• Explore real-time analytics, logs and admin dashboards
• Choose a plan and rate limit
• Do set up billing by 30 JUNE 2026, as grace period ends

📖 Migration guide: https://developers.jup.ag/docs/portal/migration

Separately, we apologise for all unaccounted downtime during migration today. We faced a few unexpected issues/limitations and had to rollback/fix.

If you have any issues or questions, please reach out to us via the support channels.

🚨 ACTION REQUIRED - Prediction Markets API Breaking Changes

Deadline: April 10, 2026

1. markets[].metadata field removal

The nested metadata object on market items is being removed from all /events/* and /markets GET endpoints.

Required action: Remove .metadata from your field paths. All fields are already available at the top level:

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

If you don't migrate: Any code reading markets[].metadata.* will return undefined after April 10.

2. Minimum order size increase ($1 → $5)

Required action: Ensure all order amounts are ≥ $5.
If you don't update: Orders below $5 will be rejected after April 14.

Questions or issues? Reach out via Discord or our support channels

New Tokens Express Verification API

If you're a Launchpad, DEX, Trading Platform or Agent: you can now submit express token verifications for programmatically.

1. Craft + sign a payment tx (burns 1000 JUP)
2. Submit verification + metadata updates together

Docs: https://dev.jup.ag/docs/tokens/verification
API Reference: https://dev.jup.ag/docs/api-reference/tokens/verify-check-eligibility

If you have specific verification needs, reach out to our VRFD account on X: https://x.com/jup_VRFD

Pump.fun gasless swaps temporarily disabled

If you sponsor gas on Pump.fun swaps (anyone other than the end user as fee payer), quotes have been returning errors since April 27. We disabled the path while patching a rent reclaim vulnerability that was draining payer wallets of SOL. Hotfix went live immediately. Program upgrade for the proper fix is in progress; we'll post here when it ships.

Two safeguards worth implementing going forward:

1. Only proceed with quotes where rentFeeLamports can be recouped through fees or otherwise
2. Reject quotes where rentFeeLamports is abnormally high

Heads up: we also fixed the rentFeeLamports calculation itself. It previously missed rent from inner instructions and is now accurate via full transaction simulation.

Apologies for the late notice on this. We're working on a better process for incidents going forward.

Hi all, quick heads up for teams using Trigger API V2.

We’re shipping a breaking request validation change for price-order deposits on Thursday, May 14, 2026 at 4:00 AM UTC.

If your integration calls:

POST https://api.jup.ag/trigger/v2/deposit/craft

please make sure you send both of these fields in the request body:

{
"orderType": "price",
"orderSubType": "single"
}

Set orderSubType based on the order:

1. single = standalone price order
2. oco = OCO / take-profit-stop-loss order
3. otoco = OTOCO / conditional chain order

No change is needed for:

POST https://api.jup.ag/trigger/v2/orders/price

Keep using the deposit requestId returned by /deposit/craft when creating the order.

After the change is live, /deposit/craft requests missing orderType or orderSubType will return a 4xx.

Docs:
https://developers.jup.ag/docs/trigger/create-order

Please update/check your integration before the change goes live. If you’re unsure which orderSubType maps to your flow, reach out to @anmoldotsol and we’ll help verify.

Hi everyone, we apologize for a brief outage that caused intermittent transaction submission and landing issues across Jupiter Spot products and APIs, including Swap, Limit Order, and DCA.

The issue appears related to DNS resolution affecting our transaction landing infrastructure. We deployed a hotfix around ~45 minutes ago, and services appear to have recovered. We’re continuing to monitor and investigate the root cause, and we’ll share an incident report once complete.