Live cricket score tracking
Use Cricinfo endpoints to turn live cricket score tracking into repeatable API requests with documented inputs and JSON responses.
Turn Cricinfo — ESPN's cricket scores and scorecard service — into structured JSON: the current homepage scores feed, full match scorecards with innings and batter/bowler lines, and series schedules with standings, all with one API key.
Get live and recent Cricinfo match scores, full match scorecards, and series schedules with standings, as structured JSON.
Endpoint families
3
Documented params
4
Examples
0
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
4
Schema refs
3
{
"platform": "Cricinfo",
"endpoint": "cricinfo-scores",
"method": "GET",
"path": "/cricinfo/scores",
"auth": "apiKey"
}Use cases
Get live and recent Cricinfo match scores, full match scorecards, and series schedules with standings, as structured JSON.
Use Cricinfo endpoints to turn live cricket score tracking into repeatable API requests with documented inputs and JSON responses.
Use Cricinfo endpoints to turn match scorecard research into repeatable API requests with documented inputs and JSON responses.
Use Cricinfo endpoints to turn series standings monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Cricinfo endpoint catalog — 3 endpoints, 4 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
3 documented Cricinfo endpoints, grouped into 3 request families — Match, Scores and V1.
4 request parameters are documented across those Cricinfo endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 Cricinfo endpoints carry a documented response schema, so the JSON shape is known before you write any parsing code.
Cricinfo endpoints document their error responses (400, 404, 429 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.
2 hosted MCP tools back the Cricinfo endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/cricinfo/match
/cricinfo/scores
/api/v1/cricinfo/series
Endpoint catalog
/cricinfo/scoresReturns the current match cards in Cricinfo's public homepage snapshot, including match state, scores, and canonical scorecard URLs. This is a point-in-time feed, not a fixture archive or streaming subscription.
MCP tool cricinfo_scores
/cricinfo/matchReturns a public Cricinfo match scorecard with match state, team scores, and available innings totals and batter/bowler lines. Upcoming matches return an empty innings list. `url` must be a canonical `https://www.cricinfo.com/series/.../(full-scorecard|live-cricket-score)` URL; live-score URLs are normalized to the paired scorecard.
MCP tool cricinfo_match
/api/v1/cricinfo/seriesReturns a series's match schedule and standings from its dedicated page. `series_id` must be a canonical series identifier from a Cricinfo URL.
Related APIs
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
Media & Streaming
Turn Apple Books ebook and audiobook pages into structured data — search, catalog detail, paginated customer reviews, similar titles, author bibliographies, series listings, and chart rankings as normalized JSON. Credential-free.
Media & Streaming
Search public Ticketmaster events and browse the full discovery hierarchy by category or city, with pagination plus event, attraction, and venue detail endpoints -- including fan reviews, related attractions, trending attractions, and enhanced venue branding -- for live-entertainment research.
How to scrape Cricinfo
Crawlora's Cricinfo endpoints return normalized public Cricinfo match and series data as JSON with one API key — no Cricinfo account required.
Call /cricinfo/scores for a point-in-time snapshot of the match cards on Cricinfo's public homepage, each with a canonical scorecard url. It is not a fixture archive or a streaming subscription.
Pass a canonical Cricinfo full-scorecard (or live-cricket-score, which is normalized to its paired full-scorecard page) URL — the kind /cricinfo/scores returns — to /cricinfo/match for match state, team scores, and available innings totals with batter and bowler lines. Upcoming matches return an empty innings list.
Pass a canonical series_id (from a Cricinfo series URL) to /cricinfo/series for that series's match schedule with scores/status and its standings table with position, points, and net run rate.
FAQ
Call /cricinfo/scores for the current homepage scores feed, /cricinfo/match with a canonical scorecard URL for full match detail, or /cricinfo/series with a series_id for a schedule and standings — all return structured JSON with one API key.
No — it is a point-in-time snapshot of Cricinfo's public homepage match cards, not a fixture archive or a streaming subscription. Use the canonical url from each card with /cricinfo/match for full scorecard detail.
Match status and team names, but an empty innings list — batter and bowler scorecard lines only populate once the match has started.
No. All three endpoints read Cricinfo's own public pages and require only your Crawlora API key.