Operations
- GETMatches in play — Paginated, 100 items per page.
- GETToday's matches — Paginated, 100 items per page.
- GETTomorrow's matches — Paginated, 100 items per page.
- GETYesterday's matches — Paginated, 100 items per page.
- GETToday's matches not started — Paginated, 100 items per page.
- GETToday's matches ended — Paginated, 100 items per page.
Route reference
Operations
The t query parameter selects the operation. Parameters not listed for an operation are ignored.
t |
Operation | Required | Optional |
|---|---|---|---|
live |
Matches in play. Paginated, 100 items per page. | — | include, bookmaker_ids, utc, lang, page |
today |
Today's matches. Paginated, 100 items per page. | — | include, bookmaker_ids, utc, lang, page |
tomorrow |
Tomorrow's matches. Paginated, 100 items per page. | — | include, bookmaker_ids, utc, lang, page |
yesterday |
Yesterday's matches. Paginated, 100 items per page. | — | include, bookmaker_ids, utc, lang, page |
notstarted |
Today's matches not started. Paginated, 100 items per page. | — | include, bookmaker_ids, utc, lang, page |
ended |
Today's matches ended. Paginated, 100 items per page. | — | include, bookmaker_ids, utc, lang, page |
Includes
Comma-separated dataset names for include, without spaces:
events: match timeline (goals, cards, substitutions); see the Match Events guide — Standard, World Cup plansstats: team match statistics, one entry per team — Standard, World Cup plansodds_prematch: pre-match odds where match coverage provides them — Standard, World Cup, Odds plansodds_inplay: in-play odds for matches in play — Standard, World Cup, Odds plans
With include=odds_prematch, include=odds_inplay or both, use bookmaker_ids to select bookmakers and control their order within each market's bookmakers array. Pass comma-separated IDs without spaces: bookmaker_ids=9,2 returns only bookmakers 9 and 2, in that order; bookmaker_ids=9,3,1 uses the order 9, 3, 1; bookmaker_ids=2 selects just bookmaker 2. Returned odds remain subject to match and market coverage.
Live publication behavior
Scores and event attribution are updated independently. A score change can be visible before the goal event, scorer or assist has been published by the source, and no fixed maximum delay is guaranteed. Keep events on the normal polling cycle: if attribution is incomplete, read it again on the next scheduled poll instead of adding an immediate high-frequency events loop.
Examples
Matches in play:
GET /v2.2/livescores/?api_key=API_KEY&t=live&include=events,stats
In-play odds from bookmakers 9 and 2, in that order:
GET /v2.2/livescores/?api_key=API_KEY&t=live&include=odds_inplay&bookmaker_ids=9,2
Today's matches:
GET /v2.2/livescores/?api_key=API_KEY&t=today&utc=2
Tomorrow's matches:
GET /v2.2/livescores/?api_key=API_KEY&t=tomorrow
Yesterday's matches:
GET /v2.2/livescores/?api_key=API_KEY&t=yesterday
Today's matches not started:
GET /v2.2/livescores/?api_key=API_KEY&t=notstarted
Today's matches ended:
GET /v2.2/livescores/?api_key=API_KEY&t=ended