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

Standard-route compact match view A leanback route for regular matches that returns a header and a live snapshot together, so a compact screen can be driven by one request for the chosen matchId.
matchheaders context block The header section carries series id and name, match description, format, state, status text and start and end timestamps, which is enough to caption the compact view.
Toss, batting side and winner ids tossresults, teamdetails (batteamid, bowlteamid and short names) and winningteamid are grouped in the header, so a client can show who batted, who tossed and who won without extra lookups.
Striker and bowler pairs miniscore lists batsmanstriker, batsmannonstriker, bowlerstriker and bowlernonstriker with runs, balls, fours, sixes, overs, maidens and economy where the sample fills them.
Run rate and current-over string crr, ballsrem and curovsstats give a numeric run rate, balls remaining and a compact string of recent deliveries such as a wide marker, ready for a small status strip.
Moment and series player lists momplayers and mosplayers contain player entries with id, name, role and image ids; the field names suggest match and series honours, but the sample does not document their meaning.

Live API Demo

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

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

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.

Related operations

Guides

View Subscription Plans →