jupiter-swap-api Release 6.0.60

feat: heaven amm integration

Full changelog:
https://github.com/jup-ag/jupiter-swap-api/releases/tag/v6.0.60

jupiter-swap-api Release 6.0.62

🚨Please update to support the following Raydium breaking changes
feat: Raydium Launchlab add more accounts for upcoming breaking change
feat: Raydium CPMM add creator fee support and calculation

More details in Raydium Dev updates https://t.me/c/2754481335/14

Full changelog:
https://github.com/jup-ag/jupiter-swap-api/releases/tag/v6.0.62

Deprecation: Self-Hosted Jupiter API Binary

We’re beginning the process of deprecating the self hosted API binary as of this announcement.

This change lets us focus on providing better support and API infrastructure that scales better, supports new features beyond swap, and ensures a smoother developer experience.

What this means:
- No new versions or updates will be released going forward.
- Existing binaries will still work now, but eventually phased out.
- Developers should transition to the hosted Jupiter API via Portal, which offers free access and paid plans for higher rate limits.

If you have questions or need support migrating, let us know in Discord.

Update: Self-Hosted Jupiter API Binary

We’ve heard your feedback and are still figuring out the details.

If you’re interested in a paid version of the self-hosted API binary for trading, we’d love to get your input and feedback directly.

Please join the public discussion here: https://t.me/+HBVrLVB6BV9hMGY1

There has been a bad deployment that affects swap events parsing.

It will affect the swap events you see in the transaction, showing wrong mints or affects your parsing mechanism for other usages.

The transaction should execute as expected, only the swap event parsing has issues.

You can check the source/destination token accounts in the instruction to verify what mints were swapped.

We are working on a fix and will update.

This is fixed, apologies for the issue.

Update on the old endpoints, we will be deprecating them end of September. Please migrate to the latest as soon as possible.

Jupiter Swap API Update

The Swap API now has stricter checks when platformFeeBps and feeAccount are involved in the flow.

- If you are passing in platformFeeBps > 0 to /quote
- You must pass in a valid feeAccount to /swap or /swap-instructions

If you plan to take fees, ensure both are present. Else, if you do not plan to take fees, please remove both parameters from your usage.

If you are seeing new 400 errors from the Swap API, this is very likely the cause.

Reminder on the deprecation of old APIs.

We are deprecating feeAmount and feeMint in each route in the routePlan. As always, the outAmount already factors in these fees.

To smooth the migration, we will just show 0 for feeAmount and the input mint as the feeMint. Then, slowly, we will deprecate these attributes.

The update above has nothing to do with feeAccount and platformFeeBps. The update above only affects the fee that is calculated for each AMM per swap. This is the fee that is taken by the AMM, not by Jupiter. So, this doesn’t affect the fee you are adding on top of Jupiter swap.

Jupiter Aggregator V6 Program Update

Find the full update in Developer Docs

We have recently introduced 4 new instructions:
- route_v2
- exact_out_route_v2
- shared_accounts_route_v2
- shared_accounts_exact_out_route_v2

You can find the details in the latest IDL.
(v1 instructions will continue to be usable and valid)

---

FEATURES
With these new instructions, you are now able to:
1. Collect fees when the swap pair consists of a Token2022 mint
2. Set fee beyond the previous cap of 255 bps

---

USAGE
For Ultra Swap API integrators:
- Create Token2022 referral token accounts
- Pass in the corresponding referral account to /order

For Legacy Swap API integrators:
- Create Token2022 token accounts
- Request /quote with instructionVersion=V2
- And pass in the token account via feeAccount in /swap

The npm package with the latest schema for instructionVersion in Legacy Swap API has been published

https://www.npmjs.com/package/@jup-ag/api/v/6.0.45

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.