Livescores

Match feeds for matches in play and for the current, previous and next day. Every feed returns match objects with status, clock, scores, teams and league, and can embed datasets through include.

Open in the interactive reference

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.

Includes

Comma-separated dataset names for include, without spaces:

• events: match timeline (goals, cards, substitutions); see the Match Events guide
• stats: team match statistics, one entry per team
• odds_prematch: pre-match odds where the plan and match coverage provide them (odds theme)
• odds_inplay: in-play odds for matches in play (odds theme)

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/?user=USER&token=TOKEN&t=live&include=events,stats

Today's matches:

GET /v2.2/livescores/?user=USER&token=TOKEN&t=today&utc=2

Tomorrow's matches:

GET /v2.2/livescores/?user=USER&token=TOKEN&t=tomorrow

Yesterday's matches:

GET /v2.2/livescores/?user=USER&token=TOKEN&t=yesterday

Today's matches not started:

GET /v2.2/livescores/?user=USER&token=TOKEN&t=notstarted

Today's matches ended:

GET /v2.2/livescores/?user=USER&token=TOKEN&t=ended