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

Format-specific Hundred route A dedicated path serves The Hundred, so a client can keep its Hundred adapter separate from the standard-format commentary calls instead of mixing the two feeds.
Optional innings and tms inputs iid and tms follow the same optional pattern as the standard route, so a ticker can narrow to one innings and request a following page by passing an epoch-millisecond timestamp.
Match video list field The source example includes a matchvideos array next to comwrapper, which gives a Hundred page a place to look for related video references when the match has them.
Last-updated marker A responselastupdated value and a top-level inningsid appear in the source example, helping a client decide whether a refreshed payload carries anything new.
Placeholder-safe payload A match without commentary can come back as a single empty entry with an empty commtxt and eventtype NONE, so the response shape stays predictable while the content is empty.

Live API Demo

GET /api/project/cricbuzz-cricket/match-details-get-commentaries-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-commentaries-hundred?key=<API_KEY>&matchId=41881'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →