Kalshi matching rows now name real markets, and their outcome IDs join to market detail
GET /v1/matching-markets/sports exists so you can take a provider's exact
native references and look them up on GET /v1/markets/{market_id}. Kalshi was
the last provider where that didn't hold, and it was broken in two different
ways at once.
market_id on a moneyline row was the event ticker, and it 404s. Kalshi
lists a game moneyline as one binary market per team — "Arizona wins" and
"San Francisco wins" are separate markets. Matching folded that pair into a
single source_markets[] entry and put their shared event ticker in
market_id, which GET /v1/markets/{market_id} has never served. Each Kalshi
market now gets its own entry:
"source_markets": [
- {
- "provider": "kalshi",
- "market_id": "KXMLBGAME-26AUG272145AZSF",
- "market_name": "Arizona wins",
- "outcomes": [
- { "canonical_outcome_key": "winner:ari", "outcome_id": "KXMLBGAME-26AUG272145AZSF-AZ", "side": "yes" },
- { "canonical_outcome_key": "winner:sf", "outcome_id": "KXMLBGAME-26AUG272145AZSF-SF", "side": "yes" }
- ]
- }
+ {
+ "provider": "kalshi",
+ "market_id": "KXMLBGAME-26AUG272145AZSF-AZ",
+ "market_name": "Arizona wins",
+ "outcomes": [
+ { "canonical_outcome_key": "winner:ari", "outcome_id": "yes", "side": "yes" },
+ { "canonical_outcome_key": "winner:sf", "outcome_id": "no", "side": "no" }
+ ]
+ },
+ {
+ "provider": "kalshi",
+ "market_id": "KXMLBGAME-26AUG272145AZSF-SF",
+ "market_name": "San Francisco wins",
+ "outcomes": [
+ { "canonical_outcome_key": "winner:sf", "outcome_id": "yes", "side": "yes" },
+ { "canonical_outcome_key": "winner:ari", "outcome_id": "no", "side": "no" }
+ ]
+ }
]outcome_id was a market ticker, not an outcome reference. On spread, total
and player-prop rows — which were already one market each — both outcomes
carried the row's own market_id, so the ID was not even unique inside its own
row and side was doing all the disambiguating. Kalshi outcome IDs are now
yes / no, byte-identical to what market detail returns for the same ticker.
Why that spelling. Kalshi publishes no per-outcome identifier: every market
is binary, and a selection is (ticker, yes|no). Kalshi names that side the same
way everywhere in its own API — as a field-name prefix on the market record
(yes_bid_dollars, no_ask_dollars), as the keys of its order book
(orderbook_fp.yes_dollars / no_dollars), as taker_side on a trade, and as
side on an order. Like SX Bet's outcomeOne / outcomeTwo, these IDs are
market-scoped: read them together with the row's market_id.
What may need changing
- A Kalshi row can now appear more than once under one submarket. If you
assumed at most one entry per provider, group by
provider. The number of canonical events and submarkets returned is unchanged —min_sourcescounts distinct providers, not entries, so a Kalshi-only submarket still does not appear. - If you were piping a Kalshi moneyline
market_idintoGET /v1/markets/{market_id}it was returning 404. It now resolves. The event ticker is still available: it is the row's parent on the default Dome-compatible map asevent_ticker, andGET /v1/events/{event_id}is the route that takes it. - If you were pairing
market_idwithsidebecause the outcome IDs did not round-trip,outcome_idnow carries the same value assideand joins directly. Both fields stay.
The default Dome-compatible markets map is unchanged: Kalshi rows still
publish event_ticker plus market_tickers[], with the same values as before.
The ?kalshi_event_ticker= lookup still accepts the event ticker, and now also
accepts the event tickers of a game's spread and total markets. Polymarket,
Predict, AlphaArcade and SX Bet rows are unchanged — Kalshi was the last
provider whose matching outcome IDs did not join.