nerd

All 72 WC2026 group-stage matches with Elo prediction + odds

Filterable by group (A-L) and status (upcoming/live/final). Odds null until the upstream odds feed activates the tournament. 5-min cache. Legacy alias: GET /v1/nerd/wc2026/matches (sunset 2026-09-01).

elo_prediction carries its own freshness: valid_until, expired (true / false / null when no expiry is stated) and expired_days. Measured 2026-09-28, all 72 match_result predictions are past their valid_until, the newest by 92 days, and these routes previously carried no expiry at all; so the block read as a forecast for a match already played. Nothing is filtered; the block is disclosed, not withheld.

get/v1/wc2026/matches

Request

  • Base URL: https://api.bigballsdata.com
  • URL: https://api.bigballsdata.com/v1/wc2026/matches
  • Auth: one of:
    • API key in header x-api-key
    • HTTP bearer

Query parameters

groupstring
status'upcoming' | 'live' | 'final'
datestring

ISO date (YYYY-MM-DD) of kickoff, as a UTC calendar day unless ?tz= is set. The exact window applied is echoed in meta.date_window.

tzstring
Example:America/New_York

Optional IANA time zone name (e.g. America/Mexico_City). ?date= then selects the local calendar day in that zone. Offsets such as -05:00 are rejected with 400. Example: ?date=2026-06-11&tz=America/Mexico_City.

view'nerd'

Accepted and IGNORED. No handler reads view; the response is byte-identical with and without it (verified 2026-09-17 against production on /v1/games, /v1/wc2026/matches and /v1/wc2026/standings, modulo meta.cache_age_ms). Kept in the contract, and still tolerated by the routes, only so existing callers that send it are not broken, but do not build on it.

Response

ok

object required

Changes

No recorded changes to this operation across all 3 revisions of this API.