Finished games no longer appear on the default sports matching page, and `include_settled` now does something
GET /v1/matching-markets/sports was serving games that had already been played
alongside today's slate. On 2026-08-25 the default limit=100 page carried four
MLB games from May and June — the oldest, mlb-tb-nyy-2026-05-23, 94 days past —
mixed in with that evening's fixtures. And include_settled, the parameter that
exists to separate the two, changed nothing: absent, =false and =true
returned identical key sets with the same total.
Both are fixed, and they were the same problem. include_settled now selects
which events a request draws from:
- Default (
include_settledabsent orfalse) — events whose scheduled start has not certainly passed. That is today's games plus a one-day grace, so a late Pacific start that runs past midnight Eastern is never dropped while it is still being played. include_settled=true— the same set plus events whose game date is further in the past, including ones a venue still lists as open.
This applies to lookups (?event_id=, ?polymarket_market_slug=, …) as well as
to list mode: one parameter, one meaning. If you hold a canonical event_id for
a game that has already been played, ask for it with include_settled=true;
without the flag the lookup answers 200 with an empty markets object.
Why the game date and not the venue's status. Those months-old rows were not
a mapping error on our side. Polymarket was still actively refreshing the
94-day-old market's quote — a two-sided book at 0.42 / 0.43, restamped six
minutes before we read it — and Predict reported tradingStatus: OPEN with no
resolution. Marking them settled would have published a resolution neither
venue has. What we can say honestly is that the game was scheduled for
2026-05-23, which the canonical event key has said all along. So the endpoint
filters on the date it already holds, and nothing on the response claims a market
is closed.
Nothing was added to the response. /v1/matching-markets/sports stays
identity-only — no status, no timestamps, no dates — so pagination.total,
has_more and cursor advancement all describe the filtered set, and a cursor
issued under one setting of include_settled still cannot be replayed against
the other.