jupiter-swap-api Release 6.0.53

feat: support dynamic tick array for whirlpool
fix: Jupiter perps breaking change

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

jupiter-swap-api Release 6.0.54

fix: update tessera v quote

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

jupiter-swap-api Release 6.0.56

feat: pump upgrade

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

API Deprecation
We are phasing out these endpoints, please migrate to their respective latest.

Please reach out to @Yankee0x if you need help
- If you need help transitioning to https://portal.jup.ag.
- If you are unsure if your endpoint is the latest/official.

---

ACTION REQUIRED
We will be gradually reducing access to these endpoints over the next weeks.

- Old Quote API V6: https://quote-api.jup.ag/v6/**
- Old Tokens API: https://tokens.jup.ag
- Old Price API: https://price.jup.ag
- Token V1: https://lite-api.jup.ag/tokens/v1/**
- Price V2: https://lite-api.jup.ag/price/v2/**

Refer to documentation for more info: https://dev.jup.ag/docs

jupiter-swap-api Release 6.0.57

fix: pump swaps with shared account

https://github.com/jup-ag/jupiter-swap-api/releases/tag/v6.0.57

Introducing Jupiter Plugin

The easiest way to add end-to-end swap functionality to any web application. Try it out at: https://plugin.jup.ag

👉 Powered by Ultra
👉 No RPCs needed!!!!!!!
👉 Earn fees
👉 Fully customizable to your UI

---

Terminal tool kit has been sunset. If you're using the old Terminal, please migrate over to the latest Plugin version.

Refer to docs for integration and customization details.
https://dev.jup.ag/docs/tool-kits/plugin

X post:
https://x.com/JupiterExchange/status/1953173426740576428

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.