Get commentary filtered to one player in an innings
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the commentary lines connected to a single player within one innings of a match. All four inputs are required: matchId in the path, iid for the innings, playerId for the player and type set to batting or bowling. The response fields listed here come from a truncated source example and were not confirmed by a live probe. The comwrapper array holds items with a commentary object carrying commtxt, eventtype, inningsid, overnum, ballnbr, timestamp and commentaryformats, plus an appindex object (seotitle, weburl). In the example, entries whose eventtype is over-break also contain an oversep object with the strike and non-strike batter names and figures, bowler name and figures, battingteamname, oversummary, runs, score, wickets, ovrbatnames and ovrbowlnames. Availability depends on the match and the player's involvement in the chosen innings.
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 API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-player-commentaries?key=<API_KEY>&matchId=41881&iid=2&playerId=23016&type=batting'
Query Result
Use Cases
- Let a player-page reader open the commentary relevant to that player within a specific match and innings.
- Create a focused batter review by requesting type batting for one playerId and reading each delivery faced in order.
- Build a bowler spell breakdown with type bowling, using the oversep summaries to show runs and wickets over by over.
- Explain how a dismissal happened by pairing the scorecard with the player's own commentary lines in a post-match article.
- Collect qualitative notes for fantasy research on a chosen player, treated as commentary text rather than as official fantasy points.
Frequently asked questions
Which parameters are required for player commentary?
All four: matchId in the path, plus iid, playerId and type in the query. The sample values are matchId 41881, iid 2, playerId 23016 and type batting.
Where do I get a valid playerId?
Use the id of a player listed for the match by the match teams endpoint for the same matchId. A player id that is not part of that match should not be expected to return useful commentary.
What are the allowed values for type?
batting or bowling. The first returns commentary for the player as a batter, the second as a bowler. Both values are documented options and no other role values are listed.
What is the oversep object in the response?
In the source example, entries with eventtype over-break include an oversep object with batstrikername, batstrikerdetails, batnonstrikername, batnonstrikerdetails, bowlname, bowldetails, battingteamname, oversummary, runs, score and wickets. This comes from a source example, not a live probe, so check it on your own calls.
What if the player did not bat or bowl in the chosen innings?
The catalog does not document that case, so the result may be empty or limited. Select the innings and role from the scorecard first, and treat missing comwrapper entries as no commentary rather than as an error.
Does this endpoint support paging?
No paging parameter is documented for this operation. Only matchId, iid, playerId and type are accepted, so use the standard commentary operation with its tms parameter when you need to page through the whole feed.