Get a cricket match scorecard with batting rows by match ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the scorecard for one cricket match, selected by the required numeric `matchId` path parameter (default 40381). Take the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints. There are no query parameters, so one request targets one match and no innings, team or player filter can be sent. A probe call for matchId 40381 returned HTTP 200 with a JSON object holding a `scorecard` array, a boolean `ismatchcomplete`, an `appindex` object, a string `status` and an integer `responselastupdated`; the declared nested numeric types matched, including integral JSON numbers. The supplied source example is unverified and truncated: it shows `appindex` with `seotitle` and `weburl`, and a `scorecard` entry with `ballnbr` plus a `batsman` list whose rows include `id`, `name`, `runs`, `balls`, `fours`, `sixes`, `strkrate` (a string such as "154.55"), `outdec` (dismissal text), `iscaptain` and `iskeeper`. Bowling figures, extras and fall-of-wicket sections were not visible in that example, so confirm them against a live response before depending on them. The unit of `responselastupdated` is not documented and should not be inferred. Coverage depends on the match, so an upcoming or abandoned fixture may return a sparse body.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/cricbuzz-cricket/match-details-get-scorecard API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-scorecard?key=<API_KEY>&matchId=40381'
Query Result
Use Cases
- Render a scorecard tab inside a match center by walking the scorecard array and reading ismatchcomplete to decide whether the page keeps polling.
- Build a type-preserving scorecard adapter with parser tests that keep booleans, integers and string strike rates intact, treating empty and multi-innings fixtures as clearly labeled synthetic test data.
- Cache each scorecard together with its responselastupdated value so a worker can skip re-rendering when the counter has not changed between polls.
- Draft an automated post-match summary that lists each batter's runs, balls, fours, sixes and dismissal text for a finished fixture found through the series matches or team results endpoints.
- Load per-batter figures into a spreadsheet or notebook for editorial fact-checking before a recap article is published.
Frequently asked questions
What does the scorecard operation return?
It returns the scorecard for one match as a JSON object. A probe for matchId 40381 confirmed the top-level keys scorecard (array), ismatchcomplete (boolean), appindex (object), status (string) and responselastupdated (integer). The nested batting fields come from a truncated, unverified source example, so check them against a live response.
Which parameter is required and where does matchId come from?
Only the numeric matchId path parameter is required (default 40381). Use the matchId returned by the match list, schedule, series matches, team schedule and result, and venue match endpoints. No query parameters exist, so there is no innings or team filter.
Which fields were confirmed by the probe and which come only from the example?
The probe confirmed the five top-level keys and their types. The batter-level fields such as name, runs, balls, fours, sixes, strkrate and outdec appear only in the source example, which is truncated, so treat them as unverified until you see them in your own response.
Are the batting figures numbers or strings?
In the source example runs, balls, fours and sixes are integers while strkrate is a string such as "100" or "154.55". Parse the strike rate deliberately instead of assuming a numeric type, and keep the other values as integers.
How can I tell whether a match has finished?
Read the boolean ismatchcomplete, and show the string status alongside it. The supplied evidence does not list the possible status values, so display the text as returned rather than mapping it to a fixed set.
Can I convert responselastupdated into a date?
The probe confirms it is an integer, but its unit is not documented, so do not assume seconds or milliseconds. Use it as an opaque marker that changes when the scorecard is refreshed, and compare it with the previous value you stored.
Does the response include bowling figures or extras?
They were not visible in the supplied example, which is cut off, so this page does not promise them. Request a finished match you care about, inspect the scorecard entries, and only then build bowling or extras components.