Skip to Content
PredictorSDK

Sports matching now tells you how old its answer is

NewSDK

GET /v1/matching-markets/sports reads a matching snapshot built in the background, and published no timestamp. A lookup that matched nothing answered {"markets": {}} whether the game is genuinely unmatched across venues or the snapshot had stopped updating hours earlier — and a game listed after a freeze can never be in a frozen snapshot. That second case has happened in production, and nothing in the response could tell the two apart.

Every response, in list and lookup mode alike, now carries a snapshot block:

  {
    "markets": {},
+   "snapshot": {
+     "observed_at": "2026-09-19T21:14:07.412Z"
+   }
  }

What the value means. observed_at is when the OLDEST venue read behind the matching snapshot began — the same "when PredictorSDK read it" meaning it has on the catalog's snapshot.observed_at and on pricing.observed_at. It is the start of the read, so it never claims data is newer than it is, and it is deliberately not the time the snapshot was written: a snapshot can keep a venue's last good read for up to 10 minutes, and its write time would hide that.

What to expect. Each venue is re-read about every 30 seconds plus the time the read takes, so while matching is healthy observed_at is normally under two minutes old and never more than about 12. Anything older means matching has stopped updating: treat an event the response does not contain as unknown, not unmatched. The filtering guide has a worked check.

It describes each response. Unlike the catalog, matching has no immutable snapshot to bind a cursor to, so pages of one traversal can come from successive snapshots and the value can advance between pages. Settled events added by include_settled=true do not affect it.

observed_at is null when the age is unknown — briefly, while a snapshot written before this release is still being served. Treat null as unknown age, not as fresh.

Matching snapshots are also fresher and more complete. A snapshot used to be rebuilt once for every venue refresh, in arrival order; under load each rebuild trailed the newest venue reads by 20 to 100 seconds (measured in production). Pending refreshes are now folded into one rebuild over the newest read of every venue. And a restart of the matching worker no longer replaces the complete snapshot with one holding only the first two venues to answer: it now waits for every venue's first read (at most 90 seconds) while the previous snapshot keeps serving.

A recent observed_at says the snapshot is updating, not that every venue is in it: a venue whose reads keep failing is dropped once its last good read is 10 minutes old, and its events can then be missing from a current snapshot.

The TypeScript, Python and Go SDKs gain a SportsMatchingSnapshot type on the response; the field is a parsed date-time. Nothing was removed and no existing field changed, so a client that ignores the new block keeps working.