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
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-livescore API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-livescore?key=<API_KEY>&matchId=41881'
Query Result
Use Cases
- Maintain a selected-match score panel after discovery instead of repeatedly downloading the entire live-match list.
- Separate a focused live-score component from the full batting and bowling scorecard view, and confirm the refresh cadence before setting a polling policy.
- Render a last-wicket and partnership banner under the score from lastwkt and partnership, hiding it when both strings are empty.
- Draw a chase tracker that compares the batting side's score with target and the required rate, using ballsrem for exact arithmetic.
- Show a compact powerplay and last-overs table from the pp and performance blocks on a match detail page.
- Compare the timestamp value between two requests before redrawing a widget, after verifying how it advances for live matches.
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.