jupiter-swap-migration

To migrate Jupiter swap integrations from Metis to Swap API v2, update your base URLs to the swap/v2 endpoints and transition from the two-step quote/instructions flow to the unified /build or /order paths.

The best way to upgrade an Ultra integration to Jupiter Swap API v2 involves migrating your existing endpoints to the new /order path and adjusting renamed parameters like taker to match the v2 response structures.

The unified Build/Order/Execute path in Jupiter Swap v2 replaces the old two-step quote and instructions flow, consolidating parameter mappings and endpoint changes into a single, streamlined API transaction process.

Yes, you need to update renamed parameters such as taker when upgrading to Jupiter Swap v2, ensuring your codebase adjusts to the new response structures for a smooth transition without compatibility risks.

Yes, you can migrate directly from Metis to the /order endpoint in Jupiter Swap v2, as the migration guide provides specific paths for both Metis to /build and Metis to /order transitions.

When moving from the two-step quote/instructions flow to Jupiter Swap v2, you must account for endpoint changes and new response structures to avoid downtime, requiring a thorough post-migration checklist.