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

One-ID Hundred mini panel Only matchId is needed, so a compact Hundred score panel can be filled from a single request without choosing an innings or any filter.
Header with series, state and toss The matchheader object in the sample holds the series name and id, match state and status text, winning team id, start and end timestamps, and a tossresults block with decision and toss winner.
Striker and non-striker pairs miniscore lists batsmanstriker and batsmannonstriker with runs, balls, fours, sixes and strike rate, plus bowlerstriker and bowlernonstriker with overs, maidens, runs, wickets, economy and rpb.
Run rate and balls remaining The sample includes batteamscore (teamscore and teamwkts), crr, ballsrem and a custstatus line, which gives a score widget its headline numbers and a status sentence.
Innings score entries inningsscores.inningsscore is a list whose entries start with balls, batteamid, batteamshortname, inningsid and isdeclared, so a panel can show each innings total next to its team code.
Match and series award players momplayers and mosplayers hold player objects with id, name, role and faceimageid, which a finished-match card can use to show award winners next to the result.

Live API Demo

GET /api/project/cricbuzz-cricket/match-details-get-miniscorecard-hundred

Request cost is temporarily unavailable. No price is assumed.

View pricing

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'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →