Get the compact leanback match view for a Hundred match

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

Returns the compact leanback view of one match through the route reserved for The Hundred format. The only input is matchId, sent in the URL path. The response fields listed here come from a source example that is cut off at 4000 characters and were not confirmed by a live probe, so anything after the cut-off is unknown. The example has two top-level objects. matchheaders carries matchdesc, matchformat, matchstarttimestamp, matchendtimestamp, seriesid, seriesname, state, status, winningteamid, revisedtarget, livestreamenabled, alerttype, team1 and team2 objects (teamid, teamname, teamsname and flag fields), teamdetails (batteamid, batteamname, bowlteamid, bowlteamname), tossresults, and momplayers and mosplayers lists of player objects with id, name, role and faceimageid. miniscore carries the current or final snapshot: batsmanstriker and batsmannonstriker (runs, balls, fours, sixes, strkrate), bowlerstriker and bowlernonstriker (overs, maidens, runs, wickets, economy), batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, event, inningsid, inningsnbr and an inningsscores.inningsscore list with balls, batteamid, batteamshortname, inningsid, isdeclared, isfollowon, overs and runs. In the sample the matchformat value is HUN while matchdesc and seriesname describe a T20I series, and innings figures such as overs 19.6 and balls 120 look like six-ball overs, so use it to learn the shape and verify the values on a real Hundred fixture. Treat every field as optional.

API Features

One-parameter compact view Only matchId is needed, so a Hundred widget or second-screen card can load its whole summary with a single path value and no innings, player or paging inputs to manage.
Match header block The matchheaders object in the source example gives state, status text, match description, start and end timestamps, seriesid and seriesname, which is enough for a card title and a status line.
Team and result identifiers team1, team2, teamdetails and winningteamid expose teamid, teamname and the short team name, so a client can join the summary to its own team records and mark the winner of a finished match.
Miniscore batting and bowling snapshot miniscore lists the striker and non-striker with runs, balls, fours, sixes and strike rate, and the two bowlers with overs, runs, wickets and economy, plus crr and the team score and wickets.
Per-innings score list The inningsscores.inningsscore array carries one entry per innings with batteamshortname, runs, overs and flags such as isdeclared and isfollowon, which suits a compact scoreline.
Award player lists momplayers and mosplayers hold player objects with id, name, role and faceimageid, so a results card can name the highlighted players of a completed match when those lists are filled.

Live API Demo

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

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

Which parameter does it need?

Only matchId, sent in the URL path as a number. Take it from the match list, schedule, series, team or venue match endpoints. The default sample value is 40381 and there are no query parameters.

What is a leanback view?

It is the compact match summary the catalog describes as the match leanback for The Hundred format. In the source example it combines a match header with a miniscore snapshot, in contrast to the larger scorecard and commentary routes.

Which fields are in the response?

The source example shows matchheaders (match description, format, timestamps, series, state, status, teams, toss, award players) and miniscore (batters, bowlers, team score, current run rate, innings scores). It is cut off at 4000 characters and not probe-confirmed, so more fields may exist.

Does the sample prove Hundred scoring rules?

No. The sample reports matchformat HUN but its description and series text refer to a T20I, and values such as overs 19.6, balls 120 and ballsrem -20 look like six-ball overs. Verify the numbers on real Hundred fixtures before relying on them.

Can it be used for a match that has finished?

The example is a completed match with state Complete and a result status, and miniscore then holds the final snapshot, so a results card is possible. Whether live matches update the same fields is not shown, so test during a live fixture.

When should I use it instead of the standard leanback operation?

Use it when the matchId belongs to a match played in The Hundred format. It is the format-specific route, which lets a Hundred view avoid standard-match field assumptions.

Are all fields always present?

Do not assume so. Many values in the example are empty strings or zeros, such as tossresults and several image ids, and coverage depends on the match, so handle missing or empty values gracefully.

Related operations

Guides

View Subscription Plans →