Get text highlights (fours, sixes, wickets) for one innings of a match
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns highlights commentary for one innings of a match: the fours, sixes and wickets passages of the text commentary. The request takes matchId in the URL path, a required iid (the innings number, for example 1) and an optional htype filter. htype accepts 0 for all entries, 2 for fours, 4 for sixes, 6 for fours and sixes together, and 8 for wickets. When htype is omitted the catalog describes the result as fours, sixes and wickets, and odd htype values behave like the even value just below them. No response fields are documented for this operation: the source example is an empty JSON object and no live probe was run, so field names and item shape are unverified. Inspect a real response for your own matchId before modelling it, and treat the result as written commentary rather than video clips, because no media or playback fields are documented. The Hundred format has its own highlights operation; this one is the standard route.
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-highlights API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-highlights?key=<API_KEY>&matchId=41881&iid=1'
Query Result
Use Cases
- Draft a boundary-and-wicket text recap for the chosen innings by sending a supported htype value, or leave htype unset for the default mix.
- Help an editor locate key passages of an innings before writing a match report, without presenting the written highlights as video content.
- Add a sixes-only list to a batting-focused newsletter by sending htype 4 for the innings under review.
- Show a dismissals-only section beside a scorecard page by requesting htype 8 once for each innings.
- Run an integration test over the five documented htype values and compare how an odd value such as 3 behaves against the even value below it.
Frequently asked questions
Which parameters are required?
matchId (URL path) and iid (query) are required. htype is optional. The defaults are matchId 41881 and iid 1.
What do the htype values mean?
0 returns all entries, 2 fours, 4 sixes, 6 fours and sixes together, and 8 wickets. The catalog lists only these five values and says odd values behave like the even value below them.
What do I get if I leave htype out?
The catalog describes the default as fours, sixes and wickets. That is a mixed key-moments view, which is different from 0 (all entries).
Where do I get matchId and what is iid?
Take matchId from the match list, schedule, series, team or venue match endpoints. iid is the innings id with catalog example 1; the catalog gives no further rule for which innings numbers exist, so check the match before requesting a later innings.
What fields does the response contain?
None are documented. The source example is an empty JSON object and no live probe was run, so field names and item shape are unverified. Inspect a real response for your matchId before building a parser.
Does it return video clips?
No media fields are documented. The operation is described as highlights commentary, so plan for written passages and do not promise clips, playback or redistribution of video.
Can I use it for The Hundred?
The Hundred has its own highlights operation. Use that one for Hundred fixtures and keep this standard route for other matches so the two requests are not mixed.
Can the result be empty?
Yes. The only source example is an empty object, and coverage depends on the match and innings, so handle an empty or sparse response without treating it as a request error.