Get the full batting and bowling scorecard for a Hundred match
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the match scorecard through the route reserved for The Hundred format. The only input is matchId, sent in the URL path. The response fields listed here come from a source example that is cut off at 4000 characters and were not confirmed by a live probe, so anything after the cut-off is unknown. The example has an appindex object (seotitle, weburl), an ismatchcomplete flag, a numeric responselastupdated and a scorecard array. The first scorecard entry shows ballnbr and a batsman array in which each batter has id, name, nickname, runs, balls, fours, sixes, strkrate (a string such as 150 or 154.55), outdec (the dismissal text), iscaptain, iskeeper, isoverseas, imageid, inmatchchange, playingxichange and media or plan fields (videoid, videotype, videourl, premiumvideourl, planid, ispremiumfree, iscbplusfree). Bowling figures, extras and other innings sections are not visible in the truncated example, so do not assume them. The sample belongs to the default matchId 40381 and its title describes a USA versus Ireland T20I from 2021, so it shows the response shape but not a populated Hundred scorecard; verify values on a real Hundred fixture before building scoring or over logic. Treat every field as optional.
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-hundred API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-scorecard-hundred?key=<API_KEY>&matchId=40381'
Query Result
Use Cases
- Build a full scorecard page dedicated to supported Hundred matches.
- Validate a Hundred-specific scorecard parser instead of transferring the standard scorecard casing, envelope or six-ball-over calculations without evidence.
- Fill a batting table with runs, balls, fours, sixes and strike rate for each batter, converting the strkrate string to a number before sorting.
- Show dismissal descriptions beside each batter in a post-match report using the outdec text.
- Decide whether a cached scorecard can be treated as final by reading ismatchcomplete and responselastupdated before re-requesting the match.
Frequently asked questions
Which parameter does it need?
Only matchId, sent in the URL path. The default is 40381. There are no query parameters.
Where do I get matchId?
Take it from the match list, schedule, series, team or venue match endpoints. For this route use the matchId of a The Hundred fixture.
Which fields are in the response?
The source example shows appindex, ismatchcomplete, responselastupdated and a scorecard array whose first entry lists batsman objects with runs, balls, fours, sixes, strkrate and outdec. It is cut off at 4000 characters and was not confirmed by a live probe, so bowling and other sections are unknown.
Does the sample show a real Hundred scorecard?
No. It belongs to the default matchId 40381 and its title describes a USA versus Ireland T20I from 2021, so it shows shape only. Check real Hundred fixtures before relying on field values.
Can I reuse my standard scorecard parser?
Not without checking. Casing, envelope and over or ball arithmetic are not confirmed to match the standard operation, so keep a Hundred-specific parser until real responses show they are identical.
Is strkrate a number?
In the sample it is a string such as 150 or 154.55, so convert it before sorting or calculating. The sample does not document a number format.
How do I know whether the match is finished?
Read ismatchcomplete in the response; the sample shows true. responselastupdated is a numeric stamp that shows when the data was last updated. Confirm its unit on a real response, and treat both as optional.
Are all fields always present?
Treat every field as optional. Coverage depends on the match, and many sample values are empty strings, zeros or false flags, including the media and plan fields.