# SDKs 0.19.0 adopt the one-shape matching response (https://docs.predictorsdk.com/changelog/2026-10-04-sdk-0-19-0)

2026-10-04 · SDK, Breaking

The TypeScript, Python, and Go SDKs 0.19.0 type GET /v1/matching-markets/sports as one canonical_events shape with a source_id lookup.

The TypeScript (`@predictorsdk/client`), Python (`predictorsdk`), and Go (`github.com/PredictorSDK/sdk-go`) SDKs are released at 0.19.0. They type the new `GET /v1/matching-markets/sports` response, which uses one shape for every venue.

- **The response is `canonical_events`** (`canonicalEvents` in TypeScript, `CanonicalEvents` in Go). The `markets` field and the `PlatformMarket` type are gone. By default each event carries its full-game moneyline; set `include_submarkets` for every matched submarket.
- **Every source market has the same fields:** `provider`, `event_id` (the venue's parent, for `GET /v1/events/{event_id}`), `market_id` (for `GET /v1/markets/{market_id}`), `market_name`, `market_slug`, and `outcomes`, each mapping a native `outcome_id` to a `canonical_outcome_key`.
- **Lookups take `source_id`** (`sourceId`, `SourceID`) as `{provider}:{id}`, alongside `event_id`. The eight per-venue request fields, such as `kalshi_event_ticker` and `pred_market_id`, are removed.

The API already serves this shape, and older SDKs cannot read it: 0.18.0's Python client raises a parsing error because it requires `markets`, and its TypeScript and Go clients find no `markets`. Upgrade to 0.19.0. [Matching markets](https://docs.predictorsdk.com/concepts/matching-markets) describes the shape, and [Filtering](https://docs.predictorsdk.com/guides/filtering) the lookup rules.