Hi all, quick heads up for teams working with Jupiter's Prediction Markets API.

We're shipping the next step of the fractional contracts migration on Thursday, 4 June 2026 at 6:00 AM UTC (2:00 PM SGT, UTC+8). No downtime is expected.

What's happening

The previous migration on 27 May was step one. On-chain storage moved to micro-contracts and the new *Micro / *Decimal fields became available. This Thursday is step two: the keeper starts executing partial / fractional fills.

What this means for your integration

Legacy fields like contracts and filledContracts are floored to whole numbers, the fractional part is dropped. Until Thursday, fills are always whole numbers, so this has no effect. From Thursday onwards, fills can be fractional, and any integration reading these legacy fields will get the truncated value. The *Micro fields carry the exact amount.

Example (an order partially filled for 2.5 contracts):

filledContracts:        "2"        ← legacy, floored, do NOT use
filledContractsMicro:   "2500000"  ← exact, use this
filledContractsDecimal: "2.5"      ← exact, for display

What you need to do before Thursday

1. Order creation: send contractsMicro instead of contracts. Send exactly one quantity field per order as providing multiple of contracts, contractsMicro, or contractsDecimal is rejected. The legacy contracts field still works for whole-contract orders but cannot express fractions.

2. Reading responses: switch any calculation or accounting logic from legacy fields to their *Micro siblings:

- contracts → contractsMicro
- filledContracts → filledContractsMicro
- contractsSettled → contractsSettledMicro
- newContracts → newContractsMicro
- totalContracts → totalContractsMicro
- totalActiveContracts → totalActiveContractsMicro

Use *Micro for math, *Decimal for display.

3. Number types: *Micro values are returned as strings (u64/u128) and can exceed JavaScript's safe-integer range. Parse with BigInt or a decimal library, never parseFloat or Number. Those will silently produce wrong values for large positions.

What's not changing

USD / price fields stay in micro-USD. depositAmount is unchanged, denominated in the deposit token's native decimals (e.g. 6 for USDC).

Legacy field handling
Legacy whole-contract fields will remain available for backwards compatibility, we won't be removing them anytime soon. There is no firm deprecation date. However, they will continue to return values floored to whole numbers, so you must migrate to the *Micro fields to read accurate data from Thursday onwards.

Full migration guide: https://gist.github.com/julianfssen/322fb55fc6f1eb575a60e7e350ebe822

If you're unsure how this affects your integration, reach out to @anmoldotsol and we'll help verify.

Content API Deprecation Notice

Heads up, we are deprecating the beta Content API on 1 July 2026.
- /tokens/v2/content
- /content/feed
- /content/cooking

In the coming months, we will be sharing more about an update to the Tokens API, including a comprehensive replacement for the Content API.

If you currently rely on/or were planning to use the Content API, reach out to @9yointern. We'd love to hear your feedback and discuss how we can help.

JupiterZ integrator fees on Swap API

Hi all, quick update for teams using the /order path of the Swap V2 API

Integrator fees are now supported on JupiterZ/RFQ routes. You can pass referralAccount + referralFee like any other /order request and still receive JupiterZ/RFQ quotes when it is the best eligible route

Relevant docs:

- Changelog

- Referral fees setup/usage

Update

The Content API deprecation is now in effect. Stated endpoints are no longer publicly accessible and will return a 403

If this broke an existing integration, reach out to @nineyoi and we'll help you sort it out.

Final reminder on the Developer Platform migration (portal.jup.ag → developers.jup.ag)

The cutoff is 7th july 9am UTC. if you haven't claimed your legacy org and set up billing on the new platform yet, do it before then or your rate limits drop to free tier (1 RPS).

set up here: developers.jup.ag/portal

Reach out to @anmoldotsol / @Yankee0x for any questions

Suggested events endpoint deprecation

Hi all, heads up for teams using the Prediction Market API suggested events endpoint.

We are deprecating the wallet-specific suggested events endpoint on Friday, 10 July 2026:

GET https://api.jup.ag/prediction/v1/events/suggested/{walletAddress}

For suggested events, use the category-based endpoint instead:

GET https://api.jup.ag/prediction/v1/events/suggested

Supported query parameters: provider, category, excludedEventId, and limit.

Update your integrations before 10 July 2026 to avoid relying on the deprecated wallet-specific suggestion flow.

If you're unsure how this affects your integration, reach out to @Yankee0x / @anmoldotsol and we'll help verify.

We’ve recently add changes to our swapEvents data.

If you were parsing it, please use the latest IDL.

Hi everyone, we're experiencing 5xx errors on our trading APIs.

We are looking into it. Prelimary findings seem to point towards RPC/Teraswitch issues.

We'll work closely with our providers and update.

Affected endpoints:
/swap/v2/order/*
/ultra/v1/order/*
/trigger/v1/*

Not affected:
/swap/v1/*
/swap/v2/build

Hey all 👋

Solana Transaction V1 will be live soon, allowing larger tx size from 1,232 → 4,096 bytes.

Our plan:
• Not switching fully to v1 immediately on day 1 ourselves
• Will expose a parameter so you can opt into v1 transactions
• v0 continues to be fully supported, no plans to deprecate yet

If you have any specific plans/usage around tx v1 and would like to discuss, please reach out to us!

Solana Transaction v1 is now supported on the Jupiter Swap API!

More about Solana Transaction v1
* 4x transaction size (4,096 bytes)
* No Address Lookup Tables
* More complex routes in a single tx

Usage
* A new parameter for each swap endpoint has been added to facilitate this.
* Do note that: v1 is opt-in. v0 remains as the default.
* Docs: https://developers.jup.ag/docs/swap/advanced/transaction-versions

Reach out to us for any questions or feedback.

We've deprecated the public beta Portfolio API v1 endpoints.

The v1 API only covered Jupiter positions and didn't meet the bar for a comprehensive portfolio product. If this impacts your users, please reach out to us, your feedback will help us evaluate next steps.

We'll be deprecating the ultra-api.jup.ag hostname on 18 October.

If you are using this hostname, please migrate to
api.jup.ag/swap/v2/* equivalent paths

For example:
ultra-api.jup.ag/order -> api.jup.ag/swap/v2/order
ultra-api.jup.ag/execute -> api.jup.ag/swap/v2/execute

Reach out to us for any questions or feedback.