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

Three required inputs select one over matchId, iid and tms are all required and come with defaults (41881, 1 and 1640424493537), so the endpoint targets a single over of a single innings and can be tried straight away.
Timestamp copied from the overs list tms is the epoch-millisecond timestamp value from the over-by-over summary, which keeps the drill-down tied to a row the user just saw instead of a guessed over number.
Ball-outcome string per over osummary is a text such as '0 0 W W ' in the sample, with one token per delivery or extra, so a ball strip can be shown for the chosen over.
Runs, wickets and totals for the over Each sample row carries runs and wicketover for the over itself, with score and wickets that appear to be running innings totals, so a card can say what one over produced.
Run rate and required rate runrate and requiredrunrate are numeric fields in the sample, with requiredrunrate shown as 0 for the first innings, which supports a chase-pressure indicator for the second innings.
Two-step list-then-open flow Pairing this with the over-by-over summary gives a simple flow: list the overs of an innings, then open a chosen one with its own timestamp.

Live API Demo

GET /api/project/cricbuzz-cricket/match-details-get-over-details

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-over-details?key=<API_KEY>&matchId=41881&iid=1&tms=1640424493537'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →