Get an over-by-over summary of a cricket innings by match ID

View all Cricket Live Scores, Scorecards & Stats API endpoints →

Returns the over-by-over summary of a cricket match. The path parameter `matchId` is required (default 41881) and comes from the match list, schedule, series, team and venue match endpoints. Three optional query parameters control which part of the match is returned: `iid` is the innings id (for example 1), `tms` is the paging cursor and `restrictInningsId` is a boolean. Leave `tms` empty to load the first page; to load the next page pass an epoch timestamp in milliseconds (for example 1640883600000) taken from the `timestamp` field returned by this same endpoint. When `restrictInningsId` is true, paging with `tms` stops at the start of the innings given in `iid` and returns HTTP 204 instead of continuing into the previous innings. These behaviours come from the catalog parameter notes and are not verified by a probe, because no probe call was recorded for this operation. The source response example attached to this operation is truncated and unverified. Its visible part, from a completed under-19 ODI group match, is a `matchheaders` object (matchdesc, matchformat, state, status, seriesid, seriesname, team1, team2, teamdetails, tossresults, winningteamid and match start and end timestamps) followed by a `miniscore` object (batsmanstriker, bowlerstriker, batteamscore, crr, curovsstats, custstatus, event, inningsid, inningsnbr, inningsscores, lastwkt). The per-over list itself is not visible in that excerpt, so confirm the over field names against a real response. The example uses the plural key `matchheaders`, while the compact scorecard example uses `matchheader`.

API Features

Innings filter with iid The optional iid parameter takes an innings id such as 1, so an over summary view can focus on one innings of the match instead of the whole list.
Timestamp cursor for older overs tms is empty for the first page and an epoch-millisecond value for the next page. The cursor value comes from the timestamp field that this endpoint itself returns.
Innings-boundary stop With restrictInningsId set to true, paging stops at the start of the innings given in iid and the catalog says it returns 204, instead of running back into the previous innings.
Match header and mini-score context The source example opens with matchheaders and miniscore objects, so a page can show the teams, series, result text and current innings totals next to the over list.
Timestamps that feed over drill-down The timestamp values returned here are the tms input for the over-details operation, so each over summary row can be linked to its own detail request.
One required ID, three optional controls Only matchId is required. iid, tms and restrictInningsId can be left out, which makes a first request for a match as simple as one path value.

Live API Demo

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

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-overs?key=<API_KEY>&matchId=41881'
📢
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?

The catalog describes it as an over-by-over summary of an innings for the selected match. The truncated source example visibly shows a matchheaders object and a miniscore object; the per-over list is not visible there, so confirm its field names with a real response for your own matchId.

Which parameters are required?

Only the numeric matchId path parameter is required (default 41881). iid, restrictInningsId and tms are optional and have no documented defaults, so a minimal request can send matchId alone.

How does paging with tms work?

Leave tms empty to load the first page. To load the next page, pass an epoch timestamp in milliseconds taken from the timestamp field returned by this same endpoint. The catalog does not state the page size or the ordering rule, so check the real response before automating a loop.

What does restrictInningsId do?

When it is true, paging with tms stops at the start of the innings named in iid and the catalog says the call returns 204 rather than continuing into the previous innings. Handle a 204 as the end of that innings and not as a failure. This behaviour is documented but not probe-verified.

Has the response been verified by a probe?

No. No probe call was recorded, and the source example is truncated before the over list. Treat every field name and the paging behaviour as unverified until you have compared them with a real response.

How do I open the detail of one over?

Use the timestamp of the over as tms, together with the same matchId and iid, in the over-details operation. That operation requires iid and tms and has no over-number parameter.

Why is the header key matchheaders here but matchheader in the mini scorecard?

The two source examples use different key names for what looks like the same kind of match header block. Do not share one parser between them without checking the key name for each operation.

Related operations

Guides

View Subscription Plans →