Get a compact cricket mini scorecard by match ID

View all Cricket Live Scores, Scorecards & Stats API endpoints →

Returns a compact scorecard for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series, team schedule and result, and venue match endpoints. There are no query parameters, so one request returns one match snapshot. No probe call was recorded for this operation, so the fields below come from a source response example and are unverified; that example is truncated and covers a completed under-19 ODI group match from the ACC U19 Asia Cup 2021. It has two top-level objects. `matchheader` holds the match context: matchdesc, matchformat, state, status, seriesid, seriesname, matchstarttimestamp and matchendtimestamp (epoch milliseconds), winningteamid, revisedtarget, `team1` and `team2` objects (teamid, teamname, teamsname), a `teamdetails` object (batteamid, batteamname, bowlteamid, bowlteamname), a `tossresults` object (decision, tosswinnerid, tosswinnername) and player lists named momplayers and mosplayers. `miniscore` holds the live-style state: batsmanstriker and batsmannonstriker (id, name, runs, balls, fours, sixes, strkrate), bowlerstriker and bowlernonstriker (id, name, overs, maidens, runs, wickets, economy), batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, curovsstats (text for the current over), custstatus, event, inningsid, inningsnbr, an inningsscores.inningsscore list (batteamid, batteamshortname, inningsid, runs, wickets, overs, balls, target, isdeclared, isfollowon) and lastwkt. Some values in the sample are placeholders: the non-striker entry is zeroed with an empty name, and tossresults.decision reads 'yet to be decided' with tosswinnerid 0 although the match state is Complete. Key casing is mostly lowercase but some player keys are camelCase, so confirm names against a real response. This is a summary view, not the full innings-by-innings batting and bowling tables.

API Features

One request, one compact snapshot Only the matchId path parameter is needed. The response combines a match header and a live-style miniscore block, so a small widget does not have to join several calls.
Header with teams, series and result matchheader carries the series name, match description, format, state and result sentence, plus team1 and team2 objects with teamid, teamname and a short teamsname such as AFGU19.
Striker and non-striker batting lines The miniscore block lists runs, balls, fours, sixes and strike rate for the batsmanstriker and batsmannonstriker entries, each with a player id for joining player endpoints.
Current bowlers with economy bowlerstriker and bowlernonstriker give overs, maidens, runs, wickets and economy, with overs and economy returned as text in the sample, so a bowling strip can be drawn without the full scorecard.
Innings totals and chase target inningsscores.inningsscore lists each innings with runs, wickets, overs, balls and target, and batteamscore gives the current batting side's score and wickets for a headline.
Current-over text and last wicket curovsstats holds a short text of the current over, custstatus a status line and lastwkt a text description of the most recent dismissal, which suit a ticker or an alert.

Live API Demo

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

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

Use Cases

Frequently asked questions

What does the mini scorecard return compared with the full scorecard?

It returns a compact summary: a match header plus a miniscore block with the two batters, the two bowlers, the batting side's score, the run rate and the per-innings totals. It does not give the full batting and bowling tables for every player, so use the full scorecard operation in the match-details group when you need those.

Which parameter is required and where does matchId come from?

Only the numeric matchId in the URL path is required. Take it from the match list, schedule, series, team schedule or result, and venue match endpoints. The default 41881 is a sample identifier for a completed under-19 ODI group match.

Is the response verified by a probe call?

No. No probe was recorded for this operation, and the source example is truncated, so the field list is unverified. Confirm field names, casing and value types against a real response for your own matchId before relying on them.

Why does the sample show 'yet to be decided' for the toss on a completed match?

In the source example tossresults.decision is 'yet to be decided' and tosswinnerid is 0 although the state is Complete. The same example has a zeroed non-striker with an empty name. Treat zero ids and empty names as not available rather than as real values.

How do I read each innings total and the target?

inningsscores.inningsscore is a list whose entries include batteamid, batteamshortname, inningsid, runs, wickets, overs, balls and target. In the sample the second-innings entry (54 for 10) is listed before the first-innings entry (194 for 9), so match entries by inningsid rather than by position.

Does it support paging or filters?

No. The only documented input is the matchId path parameter, and there are no query parameters for selecting an innings or trimming fields. Request a different matchId to get a different match.

Will every match return data?

Not necessarily. Coverage varies by match, so handle empty or sparse responses. The sample is a completed match, so how fields such as the striker, the current-over text and event are filled for a match in progress is not verified here.

Related operations

Guides

View Subscription Plans →