Get the details of one cricket over by match, innings and timestamp
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the detail for a single over of a cricket match. All three inputs are required: the path parameter `matchId` (default 41881, from the match list, schedule, series, team and venue match endpoints), the query parameter `iid`, the innings id (default 1), and the query parameter `tms`, an epoch timestamp in milliseconds that identifies the over (default 1640424493537). Take `tms` from the `timestamp` field returned by the over-by-over summary operation for the same match; there is no over-number parameter. The catalog describes this operation as ball-by-ball commentary for one over. No probe call was recorded, so the fields below come from a source response example that is truncated and unverified. That example is a JSON object with an `overs` list whose rows hold batteamid, inningsid, osummary (a text of ball outcomes such as '0 0 W W '), overnum (for example 14.4 or 49.6), runs, score, wickets, wicketover, runrate, requiredrunrate and timestamp. Rows run from the newest over of innings 2 back through innings 1, and the default tms equals the timestamp of the innings 1 row with overnum 49.6. The example therefore shows over-summary rows rather than commentary text, so the catalog description and the example differ; check a real response before depending on either shape.
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-over-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-over-details?key=<API_KEY>&matchId=41881&iid=1&tms=1640424493537'
Query Result
Use Cases
- Expand an over-summary row into the text details of that over when a user taps it in a match centre.
- Keep the match, innings and validated tms together during the drill-down instead of inventing an undocumented over-number parameter.
- Show a ball strip for a chosen over by splitting the osummary text into tokens and styling wickets and boundaries.
- Mark the overs in which wickets fell on an innings timeline by reading wicketover for each row.
- Run a one-time integration check that compares a real response with the catalog's ball-by-ball description before building commentary features.
Frequently asked questions
What does this operation return for one over?
The catalog describes ball-by-ball commentary for one over. The truncated source example instead shows an overs list of summary rows with osummary, overnum, runs, score, wickets, wicketover, runrate, requiredrunrate and timestamp. Verify the real shape for your matchId before building on either description.
Where do I get the tms value?
Take the timestamp field of the over you want from the over-by-over summary operation for the same match, and send it as tms with the same innings id as iid. A tms from a different match will not identify an over in this one.
Is there an over-number parameter?
No. The documented inputs are matchId, iid and tms only. The over is identified by its timestamp, so keep the timestamp from the summary row instead of computing one from an over number.
Does it return ball-by-ball commentary text?
The catalog says so, but the source example does not show commentary text; it shows over-summary rows. Treat commentary fields as unconfirmed, and use the commentary operations in the match-details group if you need verified commentary lines.
Has the response been verified by a probe?
No. No probe call was recorded for this operation, so field names, casing and value types come only from a truncated source example. Check them against a real response before relying on them.
What do the tokens in osummary mean?
The sample shows digits, W, Wd, N and B4 separated by spaces, such as '0 N 0 0 2 Wd W 0'. Digits and W look like runs and a wicket, but the meaning of Wd, N and B4 is not documented, so map non-numeric tokens cautiously.
What are the default values for?
matchId 41881, iid 1 and tms 1640424493537 are matching sample values: the tms equals the timestamp of the innings 1 row with overnum 49.6 in the example. For any other match, supply a tms taken from that match's over summary.