Portfolio API /positions returns 200 with elements=[] + fetcherReports=[] for multiple wallets

[amitkarpe]

Summary

GET /portfolio/v1/positions/{address} is returning 200 OK with an empty payload shape for multiple wallets:

• elements: []
• fetcherReports: []
• tokenInfo: {}

This happens consistently even for the wallet used in docs examples, which suggests a backend/indexing issue (or behavior drift) rather than a wallet-specific empty state.

Environment

• Date: 2026-02-26
• Region observed from response headers: x-amz-cf-pop: SIN2-P4
• Auth: valid x-api-key (without key request returns 401 Unauthorized as expected)
• Endpoint: https://api.jup.ag/portfolio/v1/positions/{address}

Reproduction

1. Call:
   • GET https://api.jup.ag/portfolio/v1/positions/Hh2WB6rQu1vAFyRa25opVyYXgCYXrMXfeTTNxw6s68pv
   • GET https://api.jup.ag/portfolio/v1/positions/8NppHjP2E1FL6x29r3XrLA8SYfK5VQsjhxTFJxnvXocc
   • GET https://api.jup.ag/portfolio/v1/positions/jdocuPgEAjMfihABsPgKEvYtsmMzjUHeq9LX4Hvs7f3 (docs sample wallet)
2. Include header x-api-key: <valid key>
3. Observe response shape.

Observed response shape (all 3)

{
  "owner": "...",
  "date": 1772092xxxxxx,
  "duration": 199-250,
  "elements": [],
  "fetcherReports": [],
  "tokenInfo": {}
}

Additional checks

• /portfolio/v1/platforms returns 200 with 7 platforms.
• /portfolio/v1/staked-jup/{address} returns 200 (zero staked for tested wallets).
• Calls without API key correctly return:

{"code":401,"message":"Unauthorized"}

• Repeated requests (3 retries with backoff) return the same empty shape.

Why this seems suspicious

• Empty elements can be valid, but empty fetcherReports and empty tokenInfo for multiple wallets + docs sample wallet suggests fetchers may not be running or payload assembly changed.
• This also blocks diagnostics because API gives no per-fetcher status.

Request

Could you confirm whether this behavior is expected right now, or if Portfolio indexing/fetchers are degraded for this endpoint? If expected, please document the new semantics for fetcherReports and empty payload handling in the Portfolio docs.

[RemedyVI]

Adding a related but distinct data point, in case it helps narrow this down.

Symptom (different from the original report above): GET /portfolio/v1/positions/{address} is returning 200 OK, but now with an explicit failure status rather than an empty shape:

{
  "fetcherReports": [
    { "id": "jupiter-exchange-perpetual", "status": "failed", "error": "Discriminant 225 out of range for 2 variants" }
  ],
  "elements": []
}

This is a recent regression, not a long-standing limitation. The same endpoint correctly returned real open-position data (entry price, leverage, live PnL) for these same wallets as recently as 2026-09-03, 19:29 UTC. Every request since has failed identically with the error above.

Reproduced against 5 separate wallets, repeatedly over the following day (2026-09-03 → 2026-09-04), from three independent network origins (a Vercel serverless function, a direct browser fetch(), and server-side tooling). All five fail with the exact same "Discriminant 225 out of range for 2 variants" error — this points to a server-side decode failure for the jupiter-exchange-perpetual fetcher (possibly a Perps program account-layout change the indexer hasn't been updated for), not a client-side or wallet-specific issue.

status.jup.ag doesn't currently track the Portfolio API, so there's no public signal when this endpoint degrades. Flagging here since this issue is already open and covers the same endpoint — happy to share the exact wallet addresses / raw responses if useful for debugging.