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
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-player-commentaries-hundred 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'
Query Result
Use Cases
- Build a player-focused Hundred match review from a playerId and innings, listing that batter's or bowler's own lines in delivery order.
- Keep the Hundred-specific request route when a user opens commentary from a Hundred player research page, rather than falling back to the standard player commentary operation.
- Pull one batter's boundary and dismissal lines by reading eventtype values such as FOUR, SIX and WICKET for a single innings in a player profile.
- Show a bowler's spell as an over-by-over list by requesting type bowling and reading the oversep summaries, after checking how overs are numbered on real Hundred fixtures.
- Attach a per-player text timeline next to the Hundred scorecard in an editorial workflow, ordering the lines by their timestamp values.
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.