Matched events carry their schedule, lookups have their own route, platform is provider, and SDK calls return pages
Every matched event publishes scheduled_date and scheduled_start and the list filters by league, date and participant; lookups move to GET /v1/matching-markets/sports/lookup; the platform override is provider; crypto prices share the pagination envelope; SDK 0.23.0 returns pages you can iterate.
This release changes five things callers touch, and each is a break for code written against the old shape. SDK 0.23.0 ships right after the API deploy; the table at the end maps every old call to its new one.
- Every matched event says when it is scheduled.
data[]on the list and on the lookup now carriesscheduled_date, the game's calendar day in America/New_York asYYYY-MM-DD, always present, andscheduled_start, its start in UTC with milliseconds (2026-10-16T00:15:00.000Z).scheduled_startisnullwhen no venue published an exact start: Kalshi's tickers and Polymarket's slugs carry a date and no time, so a game only they list has a date and a null start, and a "time to be announced" is never published as a start. It says when the game is scheduled, not whether it has started or ended.scheduled_dateis the day the default list judges the game by. Until the new matching build has written two runs after the deploy,scheduled_startreadsnullon every event; the date is there from the first response. - The list filters.
GET /v1/matching-markets/sportstakesleague(nba,wnba,nfl,mlbornhl),scheduled_date(YYYY-MM-DD, America/New_York) andparticipant(aparticipants[].keysuch asokc, case-insensitive). They compose,pagination.totalandhas_morecount the filtered set, and a cursor works only with the filters that issued it. Participant keys are unique only within a league (lais the Rams in the NFL and the Sparks in the WNBA), so sendleaguewith it. An empty value, an unknown league or a malformed date is a400quoting it.scheduled_datereads the same population as the rest of the list, so a past day matches nothing unlessinclude_settled=true. - Lookups moved to
GET /v1/matching-markets/sports/lookup. A page of the schedule has a cursor; a lookup is one unpaginated answer that reports what each identifier found. They are now two routes with two response shapes: the list answersdata,paginationandsnapshot, and the lookup answersdata,lookupsandsnapshot, all always present.event_idandsource_idon the list route are a400that names the lookup route, and the lookup needs at least one identifier. Everything else about a lookup is unchanged: up to 100 unique identifiers, case-insensitive, every submarket by default, andinclude_settledchoosing the population. platformisprovider.GET /v1/markets/{market_id}andGET /v1/events/{event_id}take?provider=where they took?platform=, and an event answersproviderwhere it answeredplatform, so the value a matching row publishes asprovidergoes straight into both. The composite{provider}:{id}form is unchanged.?platform=is a400that namesprovider, and the409for an ambiguous identifier now advises?provider=.- Crypto prices use the shared envelope.
GET /v1/crypto-prices/binanceansweredprices,pagination_keyandtotaland tookpagination_key. It now answersdataandpaginationand takescursor, like the other paginated routes. A cursor from the old response still decodes. Alimitabove 100 is a400; it used to be clamped to 100 with a200. With no time range the route still answers the one latest price. pagination.totalisnullwhere a route cannot count. Wallet positions and crypto prices read upstreams that give no count. Positions answered0, and crypto prices the number of prices on the page, so neither was a count of the result; both now answernull, and0means empty only onGET /v1/marketsand the matching list. Followhas_moreto paginate. The field is still always present.
The SDKs generate auto-pagination from the API's cursor and pagination.next_cursor, so each of the four paginated calls (getSportsMatchingMarkets, getMarkets, getBinanceCryptoPrices, listPolymarketWalletPositions) now returns a page in place of the response body. Iterating the page walks every page and repeats the filters; its first page is data in TypeScript, items in Python and Results in Go, and the whole response, with snapshot and pagination, is response in TypeScript and Python and Response in Go. The Pagination guide and the SDK pages show each language.
| Before | After |
|---|---|
GET /v1/matching-markets/sports?source_id=… or ?event_id=… | GET /v1/matching-markets/sports/lookup?source_id=… or ?event_id=… |
GET /v1/markets/{id}?platform=kalshi and GET /v1/events/{id}?platform=kalshi | ?provider=kalshi on both |
event.platform on an event response | event.provider |
GET /v1/crypto-prices/binance?pagination_key=… and response.prices | ?cursor=… and response.data, with response.pagination |
TypeScript client.getSportsMatchingMarkets({ sourceId }) | client.lookupSportsMatchingMarkets({ sourceId }) |
Python client.get_sports_matching_markets(source_id=…) | client.lookup_sports_matching_markets(source_id=…) |
Go client.GetSportsMatchingMarkets(ctx, &…Request{SourceID: …}) | client.LookupSportsMatchingMarkets(ctx, &…LookupSportsMatchingMarketsRequest{SourceID: …}) |
getMarket({ marketId, platform }) and getEvent({ eventId, platform }) | the same with provider |
response.pagination.nextCursor loops | iterate the page: for await (const item of page) in TypeScript, for item in pager in Python, page.Iterator() in Go |
response.data on a paginated call (Python and Go) | pager.items in Python, page.Results in Go; TypeScript keeps page.data |
SDK 0.23.0 is released right after the API deploy, so upgrade it with the API. Older SDKs keep working for the calls this release did not touch. An older Python SDK (0.22 and earlier) fails to parse three responses, because its models require fields that moved, and raises a ParsingError that carries the status code and body: GET /v1/events/{event_id} (it requires platform; the response says provider), GET /v1/crypto-prices/binance (it requires prices; the response has data and pagination) and GET /v1/polymarket/wallet/positions (it requires an integer pagination.total; the response carries null). Older TypeScript and Go clients do not validate responses, so those fields read as undefined or empty rather than raising. Any older SDK that sends platform, pagination_key, or event_id or source_id to the list gets a 400 naming the replacement.