Get the compact leanback live view for a standard cricket match
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the compact live view (leanback) for one cricket match, selected by the required numeric `matchId` path parameter (default 40381). The matchId comes from the match list, schedule, series, team and venue match endpoints. No probe call was recorded for this operation and the stored source example is cut off partway through `miniscore.inningsscores`, so every field below is unverified and anything after that point is not visible. The example is a completed T20 international and has two top-level sections. `matchheaders` holds the series (seriesid, seriesname), match description and format, state and status text, start and end timestamps, `team1` and `team2` objects, a `teamdetails` block with batting and bowling team ids and short names, a `tossresults` block, revisedtarget, winningteamid, and the `momplayers` and `mosplayers` lists of player entries with id, name, role and image ids. `miniscore` holds the current snapshot: batsmanstriker and batsmannonstriker, bowlerstriker and bowlernonstriker, batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, curovsstats, event, inningsid, inningsnbr and an inningsscores list. Timestamps are epoch milliseconds and many team and player fields are empty strings or zero. The Hundred format has its own leanback operation; this one is the standard route. Nothing here promises a smaller response or a faster refresh than other match-detail operations.
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-leanback API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-leanback?key=<API_KEY>&matchId=40381'
Query Result
Use Cases
- Power a compact match-center mode for a selected matchId, with the header caption and the live snapshot taken from the same response.
- Let a user expand the compact view into a full scorecard or commentary page, keeping matchId as the shared key and without promising a smaller payload or a faster refresh.
- Fill a followed-matches row with team short names, batting team score and wickets from batteamscore, and the status sentence from matchheaders.
- Show recent-delivery chips from curovsstats in a second-screen panel, with parser tests for tokens such as the wide marker seen in the sample.
- Build a finished-match card from winningteamid, the status line and the first momplayers entry, falling back gracefully when a list is empty.
Frequently asked questions
What is the leanback view and when should I use it?
The catalog describes it as the compact live view of a match. It returns a header block and a current-snapshot block in one response, which suits a small match panel. For full batting and bowling tables, use the scorecard operations instead.
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 40381 is a sample identifier for a completed T20 international.
Is the response verified by a probe call?
No. No probe was recorded, and the stored source example is truncated inside miniscore.inningsscores. Fields after that point, and the exact shape of inningsscores entries, are unverified, so check a real response for your own matchId.
How is this different from the Hundred leanback operation?
They are separate routes. This one is the standard-match route. Use the Hundred leanback operation only for Hundred matches, and keep the two parsers separate rather than assuming identical fields.
Why are so many team and player fields empty?
In the sample, fields such as countryname, teamcolor, battingStyle and imageid are empty strings or zero. Coverage varies by match, so treat blank and zero values as not available rather than as real data.
Does the sample come from a live match?
No. It shows a completed match: state is Complete and the status text reads Ireland won by 9 runs. For an in-progress match, expect the snapshot values to change between requests; the refresh cadence is not documented.