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: live and recent scores, full match detail, series and venue schedules, player and team statistics, ball-by-ball commentary, editorial feeds, and cricket media metadata, all with one API key.
Get Cricinfo scores, scorecards, schedules, commentary, Statsguru tables, venue fixtures, news, videos, squads, grounds, and RSS feeds as structured JSON.
Endpoint families
6
Documented params
56
Examples
17
Live catalog snapshot
Active endpoints
22
Methods
GET
Required params
36
Schema refs
22
{
"platform": "Cricinfo",
"endpoint": "cricinfo-scores",
"method": "GET",
"path": "/cricinfo/scores",
"auth": "apiKey"
}Use cases
Get Cricinfo scores, scorecards, schedules, commentary, Statsguru tables, venue fixtures, news, videos, squads, grounds, and RSS feeds 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 and player statistics into repeatable API requests with documented inputs and JSON responses.
Use Cricinfo endpoints to turn series and venue fixture monitoring into repeatable API requests with documented inputs and JSON responses.
Use Cricinfo endpoints to turn cricket news and media research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Cricinfo endpoint catalog — 22 endpoints, 56 documented request parameters, and 22 published response schemas — the same catalog Docs and Playground run against.
22 documented Cricinfo endpoints, grouped into 19 request families — Records, Team and Venue, plus 16 more.
56 request parameters are documented across those Cricinfo endpoints, 36 of them required — the full input contract is public before you write any integration code.
17 of the 22 Cricinfo endpoints ship a recorded example response, and 22 carry a documented response schema — you can code against the real JSON before the first request.
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.
22 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/records
/cricinfo/team/schedule
/cricinfo/venue
/cricinfo/calendar
/cricinfo/commentary
/cricinfo/grounds
Featured endpoints
/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
/cricinfo/seriesReturns a series's match schedule and standings from its dedicated page. `series_id` must be the slug-and-ID portion of a canonical Cricinfo series URL, such as `indian-premier-league-2024-1410320`.
MCP tool cricinfo_series
/cricinfo/calendarReturns the dated international match calendar currently published by Cricinfo. It includes match-day names and the associated series labels.
MCP tool cricinfo_calendar
/cricinfo/venueReturns structured metadata, associated home teams, and the editorial profile for a public Cricinfo cricket-ground page. `url` must be a canonical `https://www.cricinfo.com/cricket-grounds/...` or legacy `/ci/content/ground/...html` URL.
MCP tool cricinfo_venue
/cricinfo/venue/matchesReturns upcoming fixtures and recent results listed on a public Cricinfo ground page. `url` must be a canonical `https://www.cricinfo.com/cricket-grounds/...` URL.
MCP tool cricinfo_venue_matches
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 scores, statistics, fixtures, commentary, and editorial 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.
Call /cricinfo/stats for normalized Statsguru tables, including player-specific queries with player=<numeric_id>, or /cricinfo/records and /cricinfo/records/index for published record tables and the records catalog.
Use /cricinfo/venue/matches for fixtures and results at a ground, /cricinfo/team/schedule and /cricinfo/team for team data, or /cricinfo/teams, /cricinfo/grounds, and /cricinfo/squads for directory and roster snapshots.
Pass a match URL to /cricinfo/commentary for recent ball-by-ball commentary, use /cricinfo/rss for official Cricinfo RSS feeds, and use /cricinfo/news, /cricinfo/story, /cricinfo/photos, /cricinfo/videos, and /cricinfo/live for public editorial and live-content metadata.
FAQ
Use /cricinfo/scores and /cricinfo/live for score snapshots, /cricinfo/match and /cricinfo/commentary for match detail, /cricinfo/series or /cricinfo/venue/matches for schedules, and /cricinfo/stats for normalized player or team statistics — 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.
Yes. Call /cricinfo/stats with the required class and type plus player=<numeric Cricinfo player identifier>; the response contains the normalized Statsguru headers and rows for that player.
Yes. Pass a canonical full-scorecard or live-score URL to /cricinfo/commentary; it returns the latest embedded ball-by-ball and editorial commentary entries, bounded by the optional limit parameter.
Yes. Pass one of Cricinfo's published news, live-score, country-story, or player-story RSS URLs to /cricinfo/rss for normalized channel and item data.
No. These endpoints read Cricinfo's own public pages and feeds and require only your Crawlora API key.