Get match commentary for The Hundred format
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns commentary through the route reserved for matches played in The Hundred format, taking matchId in the path and the optional iid (innings) and tms (epoch-millisecond paging) query parameters. The response fields listed here come from a minimal source example and were not confirmed by a live probe. That example contains a comwrapper array, an inningsid, a matchvideos array and a responselastupdated value. Its only comwrapper item is an empty placeholder commentary object with commtxt empty, eventtype NONE, inningsid 0 and a fixed timestamp, which is what a match with no commentary content looks like. The default matchId 41881 is the same sample used by the standard commentary operation, so the example does not show a populated Hundred feed.
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-commentaries-hundred API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-commentaries-hundred?key=<API_KEY>&matchId=41881'
Query Result
Use Cases
- Route a supported The Hundred fixture to this format-specific commentary operation from a multi-format match center.
- Keep a Hundred commentary adapter separate from the standard-match adapter, and validate innings and tms behavior without assuming six-ball-over semantics.
- Show a commentary not available yet state in a live-score app when only the empty placeholder entry is returned for a match.
- Place related matchvideos references beside Hundred text commentary on a highlights companion page, whenever the array is populated.
- Compare how a Hundred match feed is structured against a standard-format feed while planning a unified commentary data model.
Frequently asked questions
When should I use this instead of the standard commentary endpoint?
Use it when the matchId belongs to a match played in The Hundred format. The standard commentary operation is a separate route, and this one is the format-specific route for Hundred matches.
Which inputs does it accept?
matchId is required in the path. iid (innings ID, for example 1) and tms (epoch timestamp in milliseconds taken from the timestamp field of a returned entry) are optional query parameters. Leave tms empty to load the first page.
Why does the sample response look empty?
The source example holds a single placeholder entry with an empty commtxt, eventtype NONE, inningsid 0 and a fixed timestamp. The default matchId 41881 is not described as a Hundred fixture, so the example should be read as an empty-result shape rather than a real Hundred feed.
Does it use six-ball overs?
The catalog does not explain how overnum and ballnbr map onto the 100-ball format, so do not assume six-ball-over semantics. Validate the values on real Hundred matches before building scoring or over logic.
What does the matchvideos field contain?
It is an array in the source example, and it is empty there, so the shape of its items is not shown. Treat it as optional and check a populated match before depending on specific video fields.
Is every Hundred match covered?
Do not assume it. Coverage depends on the fixture, and the endpoint can return an empty placeholder entry, so handle missing or empty commentary gracefully.