Get text highlights for one innings of a Hundred match
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns highlights commentary for one innings of a match, through the route reserved for The Hundred format. The request takes matchId in the path, a required iid (the innings number) and an optional htype filter: 0 returns all entries, 2 fours, 4 sixes, 6 fours and sixes, and 8 wickets. When htype is omitted the catalog describes the result as fours, sixes and wickets, and odd htype values behave like the even value 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 the field names and item shape are unverified. Inspect a real response for a Hundred fixture before modelling it, and treat the result as text commentary rather than video clips, because no media or playback fields are documented.
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-hundred API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-highlights-hundred?key=<API_KEY>&matchId=40381&iid=1'
Query Result
Use Cases
- Prepare an innings-specific text-highlight review for a Hundred match using a validated htype value for the chosen iid.
- Offer a format-aware written recap on a Hundred match page without implying that this commentary operation supplies video clips or playback rights.
- Build a wickets-only timeline for a post-match summary by requesting htype 8 once per innings.
- Power a boundaries tab in a Hundred match center that lists fours and sixes together with htype 6 for the selected innings.
- Compare the key moments of innings 1 and innings 2 by calling the route twice with different iid values when drafting a chase-versus-defence write-up.
Frequently asked questions
Which parameters are required?
matchId in the URL path and iid (the innings number) as a query parameter are required. htype is optional. The defaults are matchId 40381 and iid 1.
What do the htype values mean?
0 returns all entries, 2 returns fours, 4 returns sixes, 6 returns fours and sixes together, and 8 returns wickets. Odd values behave like the even value below them, so 5 acts like 4.
What do I get if I leave htype out?
The catalog describes the default as fours, sixes and wickets. That is different from htype 0, which is documented as all entries, so send 0 explicitly when you want everything.
What fields does the response contain?
None are documented. The source example is an empty JSON object and no live probe was run, so the item shape is unverified. Call it for a real Hundred fixture and inspect the result before you model fields.
Does it return video clips?
The operation is described as highlights commentary and no video, media or playback fields are documented, so treat it as text. Do not promise clip delivery or redistribution rights from this route.
When should I use it instead of the standard highlights operation?
Use it when the matchId belongs to a match played in The Hundred format. It is the format-specific route and keeps a Hundred recap separate from the standard-format highlights request.
Can the result be empty?
Yes, plan for it. The example itself is an empty object, and coverage depends on the fixture and innings, so show a no highlights yet state instead of assuming entries exist.