Skip to Content
PredictorSDK

Matching responses list events in data and report every lookup

GET /v1/matching-markets/sports returns events in a data array in start order, reports what each lookup identifier found, returns a lookup's events in full, and labels outcomes as market detail does.

BreakingNewFix

Using GET /v1/matching-markets/sports the way a client does turned up no wrong mappings, but several things that made it harder to use than it should be. This release fixes them. The response shape changes, so update to SDK 0.21.0, released right after this deploy.

Events are in data, in start order. The canonical_events map is now the data array, soonest scheduled start first: the same field, and the same order, as every other paginated endpoint. A map could not keep that order, so finding the next games meant sorting by a time the response does not include. Each event appears once.

A lookup reports what each identifier found. A lookup used to key events by the identifier you sent, so an event found by two identifiers came back twice, and learning which identifiers missed meant diffing your own inputs against the keys. Now lookups lists every event_id and source_id you sent, as you sent it, with the events it found:

"lookups": {
  "kalshi:KXNBAGAME-26OCT20OKCSAS": { "event_ids": ["nba-okc-sas-2026-10-20"] },
  "sxbet:L19766755": { "event_ids": ["nba-okc-sas-2026-10-20"] },
  "kalshi:KXNBA-27-SAS": { "event_ids": [] }
}

A lookup returns its events in full. include_submarkets now defaults to true for a lookup, so looking up a spread ticker returns the spread rather than only the game's moneyline. A list page still defaults to the moneyline, which keeps it small. Send the flag to choose either way.

Labels mean what market detail says they mean. A Kalshi or Pred outcome is labelled with its side, Yes or No, as GET /v1/markets/{market_id} names it. It used to repeat the market's title on both sides, which read as if the No side backed the team in the title. The title is in market_name. An SX Bet market is now named by its two outcome labels (Dallas Cowboys -6.5 vs Tampa Bay Buccaneers +6.5), as market detail titles it: SX Bet's own name for a market is the game's team pair, shared by the moneyline and every spread and total.

Also in this release:

  • Submarkets are listed full game first, then each half and quarter, with the moneyline, spreads, totals and props in that order. Outcomes list the away team, the cover side and the over first.
  • Fields that are always present are marked required: an event's sport, league and participants, a source market's market_name, and every outcome's label and outcome_id.
  • A Polymarket condition ID, the condition_id that wallet positions carry, works as source_id=polymarket:<condition_id> and on GET /v1/markets/polymarket:<condition_id>.
  • A player prop's own market_id finds its game under the default strict policy too. It used to find nothing unless you sent player_prop_match=same_prop.
  • New 400s, each quoting the value: an outcome ID that names a side in every market of its venue (kalshi:yes, sxbet:outcomeOne), which points you to the market's market_id; a control parameter sent twice (limit=1&limit=50 used to apply the first); and an event_id that matches no event but is a venue's identifier, most often a Polymarket slug that carries a night game's UTC date, which names the provider to send it under.
  • GET /v1/events/{event_id} returns every nested market_id platform-native, as documented. AlphaArcade, ProphetX, Pred, Hyperliquid and Limitless returned it with the provider prefix, so on three venues a matched market's market_id was not among its own event's markets. Send the event's platform with a nested ID to market detail.
  • The docs site's /llms.txt lists every page again (it was serving [object Promise]), and /llms-full.txt includes each API reference page's description.

What to change

BeforeNow
canonical_events[event_id] in list modedata[], each event with its event_id
canonical_events[identifier] in lookup modelookups[identifier].event_ids, with the events in data
An identifier that matched nothing: absentListed in lookups with "event_ids": []
A lookup returned the moneyline unless include_submarkets=trueA lookup returns every submarket unless include_submarkets=false
Kalshi and Pred outcome label: the market titleYes or No; the title is market_name
SX Bet market_name: the team pairIts two outcome labels
/v1/events nested alpha-arcade:<id>, prophetx:<id>, …<id>, sent to market detail with the event's platform

On this page