Skip to Content
PredictorSDK

Documented example identifiers refreshed, and short-lived ones spent only where the shape needs them

Fix

Every expired example identifier in the API reference and the guides has been refreshed against live data. The canonical event key behind the matching endpoint's rich canonical_events example had expired, along with its Polymarket slug, its Kalshi event ticker, and the Polymarket MLB game slug used on /v1/markets/{market_id}, /v1/events/{event_id} and the polymarket_market_slug filter. All of them now resolve.

The interesting part is which example got which identifier. Cross-source depth only exists for imminent games — the venues list a spread days ahead, not months — so the richest example is always the shortest-lived one. Re-measured across 103 live canonical events, the furthest-dated event carrying a spread with three independent sources was one day out, while the furthest-dated event of any kind was nearly two months out and carried a single moneyline. Standing one game in for every example therefore spends the shortest lifetime everywhere.

Each site now gets the longest-lived identifier that still carries the shape it is teaching:

  • The league field's description and the "the league is the first segment" line in the docs illustrate the key format. They need no imminent game, so they use a season-opener key that resolves for weeks.
  • The list-mode example needs a Polymarket row, so it moved to the furthest-dated event that has one. It picked up a PREDICT row on the way, so the two list-mode entries now show all four matching platforms rather than three.
  • Only the include_submarkets=true example genuinely needs a three-source spread, so it is the only one carrying a short-lived key. Its replacement was chosen so the canonical key and the Polymarket slug are visibly different strings for the same game, which is the whole reason the canonical layer exists, and so the spread's subject is the home team — the side is read from each source's own labels, never defaulted.

Hyperliquid's examples are the one case that cannot be fixed by refreshing. Its entire live catalog is a handful of daily-recurring outcomes, so any specific integer id is valid for about a day and a "current" one is wrong again tomorrow. Those examples keep their ids and now say so in the example summary itself — which the SDKs and this site render — instead of only in a comment in the raw spec.

No API behaviour changed. The SDKs are regenerated because the descriptions and examples they embed come from the spec.