Live fixture monitoring
Use LiveScore endpoints to turn live fixture monitoring into repeatable API requests with documented inputs and JSON responses.
Combine real-time fixtures and score data with sport, competition, team, daily, prediction, and publisher-linked LiveScore news routes across 16 endpoints.
Extract LiveScore live scores, sports, competitions, matches, teams, players, news, and publishers as structured JSON.
Endpoint families
6
Documented params
41
Examples
16
Live catalog snapshot
Active endpoints
16
Methods
GET
Required params
29
Schema refs
16
{
"platform": "LiveScore",
"endpoint": "livescore-live-scores",
"method": "GET",
"path": "/livescore/live-scores",
"auth": "apiKey"
}Use cases
Extract LiveScore live scores, sports, competitions, matches, teams, players, news, and publishers as structured JSON.
Use LiveScore endpoints to turn live fixture monitoring into repeatable API requests with documented inputs and JSON responses.
Use LiveScore endpoints to turn match and player analysis into repeatable API requests with documented inputs and JSON responses.
Use LiveScore endpoints to turn competition news aggregation into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live LiveScore endpoint catalog — 16 endpoints, 41 documented request parameters, and 16 published response schemas — the same catalog Docs and Playground run against.
16 documented LiveScore endpoints, grouped into 16 request families — Competition, Competitions and Live Scores, plus 13 more.
41 request parameters are documented across those LiveScore endpoints, 29 of them required — the full input contract is public before you write any integration code.
16 of the 16 LiveScore endpoints ship a recorded example response, and 16 carry a documented response schema — you can code against the real JSON before the first request.
LiveScore endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
16 hosted MCP tools back the LiveScore endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/livescore/competition
/livescore/competitions
/livescore/live-scores
/livescore/match
/livescore/match-stats
/livescore/news
Featured endpoints
/livescore/sportsLists the five sports in LiveScore's fixture navigation, with no inputs. The ids are `soccer` (shown as Football on the site), `hockey`, `basketball`, `tennis` and `cricket`. Use an id as the sport input of the LiveScore scores endpoint.
MCP tool livescore_sports
/livescore/live-scoresReturns current live sections for a supported sport. Empty Sctns is a valid result when there are no live events. Use Nav and the final section Id for cursor paging.
MCP tool livescore_live_scores
/livescore/scoresReturns either the unpaged full-day scoreboard or one cursor-paged UI-style section page for a supported sport and date. The response's Nav values indicate whether another page is available; use the last returned section Id as cursor. Sport ids are discoverable from /livescore/sports.
MCP tool livescore_scores
/livescore/scores-tocReturns the event, player, section, and competition identifiers indexed by a sport and date. These IDs are date-specific and can help callers enumerate score-page sections.
MCP tool livescore_scores_toc
/livescore/searchSearches the public LiveScore index for a free-text term, or browse its current team, competition-stage, and region-category sections with an empty query. Results are dynamic, limited per section, and are not a complete historical competition directory. Use /livescore/sports to discover all supported sport tokens.
Response notes
- Results retain LiveScore's current JSON shape under `results`. Depending on the sport and query, the source may return `Teams`, `Stages` (competition stages), and `Categories` (region or competition groups); a section can be absent when that sport has no corresponding result group. - When present, `results.Sorting` contains a subset of `Teams`, `Stages`, and `Categories`, in the source's preferred display order. - An empty query returns the anonymous search index's current browse groups. Cold replays with `limit=50` returned 19/28/28/15/24 categories for soccer/hockey/basketball/tennis/cricket respectively on 2026-09-27. These are dynamic search-index results, not a complete historical competition directory; use `/api/v1/livescore/competitions` for the public English competition sitemap paths it covers. - `limit` is validated from `1` to `100`; the caller can raise it above the upstream UI's observed `20` value, but the source may still return fewer records. - Results use the anonymous public search feed and English locale. The response does not pin a country code, so callers are not restricted to the browser's observed region.
MCP tool livescore_search
/livescore/competitionsReturns English competition pages listed in LiveScore's public competition sitemaps plus competition-shaped pages listed in the English cricket sport sitemap. The sitemap index has dedicated competition sitemaps for soccer, hockey, basketball, and tennis; cricket discovery remains partial and dynamic.
MCP tool livescore_competitions
Related APIs
Media & Streaming
Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.
Media & Streaming
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
How to scrape LiveScore
LiveScore’s public navigation exposes five top-level sports: football, hockey, basketball, tennis, and cricket. Its news sitemap also distinguishes sport, competition, team, daily, prediction, promotion, and publisher-linked routes. A competition or team route is the better collection boundary for a tournament dossier; daily and prediction pages serve a different editorial purpose.
Call /livescore/sports, then use its ids with score endpoints; soccer is the API token for the site’s Football section.
Use competition, match, match-stats, team, player, and search endpoints to move from a fixture into its related public entities.
Call /livescore/news-categories before /livescore/news because the sitemap-derived category value changes with sport, competition, team, daily, and promotion pages.
FAQ
The documented sport ids are soccer, hockey, basketball, tennis, and cricket. LiveScore uses soccer as the API token for Football.
Yes. The endpoint family includes live scores and match data plus news categories, news pages, feed records, article metadata, and publisher data.
News category IDs come from the current sitemap and can include competition, team, daily, prediction, and promotion paths. Use the category endpoint as the source of valid current values.
No. LiveScore does not run a self-serve developer program; its real-time data is only available through its own apps and site, or through paid third-party sports-data resellers. Crawlora reads LiveScore's own public pages directly instead, with no reseller contract needed.