Get commentary lines for one batter or bowler in a Hundred innings

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

Returns the text commentary lines that involve one chosen player in one innings of a match, through the route reserved for The Hundred format. The request takes matchId in the path and three required query parameters: iid (the innings number), playerId (a player taking part in that match, found through the match teams endpoint) and type, which must be batting or bowling to select the player's role. 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. That example shows an appindex object (seotitle, weburl) and a comwrapper array. Each comwrapper item holds a commentary object with commtxt, eventtype (NONE, FOUR, WICKET, or a combined value such as over-break,SIX), inningsid, overnum, ballnbr, batteamscore, boundarytracker, timestamp, commentaryformats (bold id and value pairs such as B0$ and B1$) and media reference fields (videoid, videotype, videourl, premiumvideourl, imageid, planid, ispremiumfree). Over-break entries add an oversep object with oversummary, runs, wickets, score, batstrikername, batnonstrikername, battingteamname, bowlname and bowldetails. The default values (matchId 40381, iid 1, playerId 11131, type batting) belong to a sample whose lines describe a T20I with six-ball overs, so the example does not show a populated Hundred feed. Treat every field as optional.

API Features

Hundred-format player route A dedicated route filters commentary to one player for The Hundred, so a Hundred player page keeps its own request instead of silently calling the standard player commentary operation.
Batter or bowler role switch The required type parameter accepts batting or bowling, which lets the same matchId, iid and playerId return the player's deliveries faced or the deliveries they bowled, depending on the role you choose.
Every input is required matchId, iid, playerId and type are all required, so a request always names one match, one innings, one player and one role and there is no unfiltered fallback to handle.
Event-tagged delivery lines Each commentary item carries an eventtype (the source example shows NONE, FOUR, WICKET and over-break,SIX) plus overnum, ballnbr and a millisecond timestamp, which makes boundaries and dismissals easy to pick out.
Over summary blocks Over-break items include an oversep object with the over's oversummary string, runs, wickets, running score, strikers and bowler figures, giving a bowler or batter view a ready-made over-by-over recap.
Marker-based bold text commtxt can contain markers such as B0$ that map to id and value pairs in commentaryformats, so a client can render words like out, FOUR or a dismissal line in bold.

Live API Demo

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

Use Cases

Frequently asked questions

Which parameters are required?

All four. matchId goes in the URL path, and iid, playerId and type are required query parameters. The defaults are matchId 40381, iid 1, playerId 11131 and type batting.

Where do I get playerId?

Use the id of a player in the same match, as listed by the match teams endpoint for that matchId. The sample playerId 11131 is the player named in the example commentary lines; a player who did not take part in the match is not a meaningful value.

What values can type take?

Only batting or bowling. batting selects commentary for the player as a batter and bowling selects commentary for the player as a bowler. Any other value is outside the documented options.

How is this different from the standard player commentary operation?

It has the same four-input shape but is the route reserved for The Hundred format. Use it when the matchId belongs to a Hundred fixture so your Hundred player view does not mix with the standard-format request.

Does the sample show a real Hundred feed?

No. The sample belongs to the default matchId 40381 and its lines describe a T20I with overnum values such as 18.5, so it demonstrates the response shape only. It is also cut off at 4000 characters and was not confirmed by a live probe.

Can I assume five-ball sets or 100-ball logic from overnum?

No. The catalog does not explain how overnum and ballnbr map onto the 100-ball format, and the sample uses six-ball style numbers. Validate the values on real Hundred matches before building scoring or over logic.

Which fields should I treat as optional?

All of them. Coverage depends on the match, so a player may have few or no lines, oversep appears only on over-break entries, and the media fields in the sample are zero or empty strings.

Related operations

Guides

View Subscription Plans →