Get the live score panel for one cricket match by match ID

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

Returns the live score data for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). The matchId comes from the match list, schedule, series, team and venue match endpoints. No probe call was recorded for this operation, so the fields below come from a source response example and are unverified. The example is a completed under-19 ODI, so it shows the final state rather than an in-progress score. The response has a `comwrapper` array holding the latest commentary entry (commtxt, eventtype, overnum, ballnbr, inningsid, timestamp and a commentaryformats list), an inningsid, an empty `matchvideos` array and a `miniscore` object. The miniscore carries the current batters (batsmanstriker, batsmannonstriker) and bowlers (bowlerstriker, bowlernonstriker) with runs, balls, overs, wickets and economy, `batteamscore` (teamid, teamscore, teamwkts), crr, rrr, target, ballsrem, oversrem, custstatus, event, lastwkt, partnership, a `performance` list (for example last 5 and last 10 overs), a `pp` powerplay block, an `inningsscores` list (runs, wickets, overs, balls, target, isdeclared, isfollowon per innings) and a timestamp. A responselastupdated field appears at the top level and inside miniscore with different values, and its unit is not documented. This is a focused score panel, not the full batting and bowling scorecard.

API Features

Focused single-match score panel One request for a chosen matchId returns the score snapshot and the newest commentary entry together, so a score widget does not need the whole live-match list.
Latest commentary in comwrapper The comwrapper array holds the most recent entry with commtxt, eventtype (WICKET in the sample), overnum, ballnbr and a timestamp, which can drive a last-ball line under the score.
Current batters and bowlers miniscore lists the striker and non-striker with runs, balls, fours, sixes and strike rate, and both bowlers with overs, runs, wickets and economy, as filled in the sample.
Chase fields: target and rates target, crr, rrr, ballsrem and oversrem sit in the miniscore, which supports a chase tracker once you check which of them are populated for the match state you serve.
Last wicket and partnership text lastwkt holds a dismissal line with the score and over at the fall of the wicket, and partnership holds the current stand, which suits a short situation banner.
Powerplay and recent-overs blocks The pp block lists powerplay type, over range, runs and wickets, and the performance list gives labelled runs and wickets for the last 5 and last 10 overs in the sample.
Per-innings score entries inningsscores gives runs, wickets, overs, balls, target and declared or follow-on flags for each innings, so both sides of a result can be drawn from the same response.

Live API Demo

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

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-livescore?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

Which parameter does it need?

Only the numeric matchId in the URL path. 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, so the field list comes from a source response example for a completed match. Check field names and value types against a real response, ideally for a match that is in progress, before building on them.

How is live score different from the leanback and scorecard operations?

Live score returns the current score snapshot plus the latest commentary entry. The leanback operation adds a match header with toss and award lists, and the scorecard operations return full batting and bowling tables. Pick the one that matches the screen you are building.

Does it return every batter and bowler in the innings?

No. The sample shows only the current striker, non-striker and two bowlers inside miniscore, plus one commentary entry. For all batting lines and dismissals, use the scorecard operation for the same matchId.

How often should I poll it?

The refresh cadence is not documented and no probe measured it. Start with a conservative interval, compare the timestamp values between responses, and tune after observing a real live match.

Why does the sample show overs of 49.6?

In the sample one innings has overs 49.6 with balls 300, which is a full 50 overs. Use the balls value when you need exact arithmetic and treat overs as a display string.

What do the two responselastupdated values mean?

The sample has responselastupdated 0 at the top level and a ten-digit number inside miniscore. Their unit and meaning are not documented, so do not use them for freshness logic until you have checked live responses.

Related operations

Guides

View Subscription Plans →