# Polymarket's Protocol V2 markets are read (https://docs.predictorsdk.com/changelog/2026-10-15-polymarket-protocol-v2)

2026-10-15 · Fix

Polymarket began listing markets on a second position system, Protocol V2, on October 14. The catalog, market detail, events and matching now read them.

Polymarket began listing markets on Protocol V2, its second position system, on October 14, starting with a pilot of crypto and weather markets. Polymarket's market API returns those markets only to a request that asks for them, so until this change PredictorSDK never read them: they were missing from `GET /v1/markets`, `GET /v1/markets/{market_id}` and `GET /v1/events/{event_id}` answered `404` for a V2 market's slug or condition ID, and a resolved V2 market read `closed` instead of `settled`.

- **Catalog and matching** read both position systems, so V2 markets appear in `/v1/markets`, and a game Polymarket lists on V2 is matched like any other.
- **Market detail** finds a V2 market by its numeric ID, slug or condition ID, so a wallet position held in a V2 market can be priced. A resolved V2 market reads `settled`.
- **Outcome IDs.** A V2 market's `outcome_id`s are its position IDs, the IDs Polymarket trades it by. A market on Polymarket's original system keeps its CLOB token IDs.
- **Events** find a V2 event by its slug.

Nothing changed shape, so nothing is breaking, and Polymarket's existing markets read exactly as before. The rest of Polymarket's V2 migration (a new exchange contract, order signing and approvals) concerns trading on Polymarket, which PredictorSDK does not do.