Get ball-by-ball match commentary, optionally by innings
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the text commentary feed for one cricket match identified by matchId. Optionally restrict the feed to a single innings with iid, and page through it by passing the epoch-millisecond timestamp of a previously returned entry as tms; leave both empty to load the first page. 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 (for example NONE or WICKET), inningsid, overnum, ballnbr, batteamscore, timestamp, commentaryformats and media reference fields such as videoid, imageid and videourl. The example also shows an appindex object (seotitle, weburl) and a buzz object (applink, imageids, isbuzzenabled, position). Commentary availability depends on the match, so 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-commentaries API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-commentaries?key=<API_KEY>&matchId=41881'
Query Result
Use Cases
- Power an innings-selectable text match center for the chosen matchId by switching iid between the first and second innings.
- Build a live ticker that remembers the newest timestamp it received and requests more entries through tms, after validating the paging direction on your own matches.
- Extract WICKET events from the commentary to draw a dismissal timeline beside the scorecard in a post-match report.
- Feed commentary text into an internal search or summarization workflow for analysts, once you have confirmed your own usage rights for the text.
- Render bold highlights in a custom commentary view by resolving the B0$ style markers in commtxt through commentaryformats.
Frequently asked questions
Which parameter is required to fetch match commentary?
Only matchId, which is sent in the URL path as a number. Take it from the matchId field of the match list, schedule, series, team or venue match endpoints. The sample value is 41881. iid and tms are optional query parameters.
How do I load the next page of commentary?
Leave tms empty to load the first page, then pass an epoch timestamp in milliseconds taken from the timestamp field of a returned entry. The catalog does not state whether this returns older or newer lines. In the source example the entries are listed newest first, so check the behavior on your own matches before building a ticker around it.
What does the iid parameter do?
iid is the innings ID, for example 1. When it is set the feed is restricted to that innings; when it is omitted no innings filter is sent. Each commentary entry also reports its own inningsid.
Why does commtxt contain markers like B0$?
In the source example, commtxt holds placeholders such as B0$ and B1$, and commentaryformats lists matching id and value pairs, for instance the bold text out or Lbw. A client that wants formatted text should substitute those values and fall back to the raw commtxt when no format is present.
Can the response be empty or incomplete?
Yes. Commentary depends on the match and its coverage, and the field list above comes from a truncated source example rather than a live probe. Handle missing arrays and fields, and use the separate Hundred commentary operation for matches played in that format.
How is this different from the player-filtered commentary operation?
This operation returns the commentary feed for the match or a chosen innings. The player-filtered operation instead requires iid, playerId and a batting or bowling type and returns commentary tied to one player.