Get the compact mini scorecard for a Hundred match
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the compact mini scorecard of one match 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 two top-level objects. matchheader carries matchdesc, matchformat, matchstarttimestamp, matchendtimestamp, seriesid, seriesname, state, status, winningteamid, revisedtarget, livestreamenabled and alerttype, team1 and team2 objects (teamid, teamname, teamsname and flag fields), teamdetails (batteamid, batteamname, bowlteamid, bowlteamname), tossresults (decision, tosswinnerid, tosswinnername), and momplayers and mosplayers lists of player objects with id, name, role, faceimageid and teamname. miniscore carries the snapshot: batsmanstriker and batsmannonstriker (runs, balls, fours, sixes, strkrate), bowlerstriker and bowlernonstriker (overs, balls, maidens, runs, wickets, economy, rpb), batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, custstatus, event, inningsid, inningsnbr and an inningsscores.inningsscore list that begins with balls, batteamid, batteamshortname, inningsid and isdeclared. The sample reports matchformat HUN while matchdesc and seriesname describe a T20I series, its inningsscore shows 120 balls, which is more than a 100-ball innings, and it pairs inningsid 2 with inningsnbr 1st inn, so use it to learn the shape and verify the values on a real Hundred fixture. The header object is named matchheader (singular) in this sample; confirm the name before sharing a parser with other compact match views. 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-miniscorecard-hundred API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-miniscorecard-hundred?key=<API_KEY>&matchId=40381'
Query Result
Use Cases
- Populate a compact Hundred scorecard panel for a selected match.
- Offer a drill-through from the mini panel to the Hundred full-scorecard operation without assuming the two responses have identical fields.
- Drive a score-strip row that shows team score, wickets, current run rate and the batters at the crease for a followed fixture.
- Build a result card for a finished fixture from state, the status sentence, winningteamid and the award player lists.
- Test a Hundred widget parser against the sample quirks, such as HUN format beside T20I labels and inningsid 2 beside 1st inn, before trusting field combinations.
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 a matchheader object (teams, series, state, status, toss, award players) and a miniscore object (batters, bowlers, team score, crr, ballsrem, event, innings scores). It is cut off at 4000 characters and was not confirmed by a live probe, so later fields are unknown.
Does the sample prove Hundred scoring rules?
No. matchformat is HUN but the sample describes a T20I series, its inningsscore shows 120 balls and inningsid 2 sits next to inningsnbr 1st inn. Use it for field names and verify values on a real Hundred fixture.
How is it different from the Hundred full scorecard?
This is the compact snapshot with header, current pair and innings totals. The full scorecard operation returns per-batter lines and is a separate response, so do not assume identical fields between the two.
Can I use it for a finished match?
The sample describes a completed match (state Complete with a result status and winning team id), so a finished fixture can return a result snapshot. What other states return is not confirmed.
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, for example the toss decision reads yet to be decided.