Get cricket records such as most runs by statsType (default mostRuns), optionally narrowed by matchType, team, opponent and year, as a headers array plus player rows

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

Returns a cricket record table for one record type. statsType is the only required input: a query string whose default mostRuns is the documented example value, and whose accepted values come from the value field of the record filters operation of this product. Four optional numeric query filters narrow the table: matchType (the matchTypeId from the filter.matchtype list of this operation's own response), team and opponent (team ids from the filter.team list of this operation's own response), and year (a calendar year such as 2021). The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a filter object, a headers array and a values array. In the filter object, matchtype lists matchTypeDesc and matchTypeId strings (test 1, odi 2 and t20 3 in the example), selectedMatchType is a string (t20 in the example) and team lists id and teamShortName strings (twelve teams such as IND with id 2 and PAK with id 3). The headers array is Batter, M, I, R, SR in the example, and each element of values is an object that holds its own values array of strings: the first string looks like a numeric player id, the second is the player name, and the four that follow line up with the M, I, R and SR columns. The saved example is cut off after several dozen rows, so the full row count is not confirmed, and the evidence does not say which request parameters produced it or how headers change for other statsType values. No live probe was recorded, so every response field described here comes from the source example and is not independently verified.

API Features

Record type chosen by statsType The required statsType string picks the record table, with mostRuns as the documented default and the allowed values listed by the record filters operation of this product.
Year, team, opponent and format filters Four optional numeric filters (year, team, opponent and matchType) narrow the table, so a request can describe one team's record against a single opponent in a single format or season.
Filter lists in the same response The filter object returns matchtype and team lists with ids, so the response that shows a record table also supplies the ids needed to narrow the next request.
Team ids with short codes filter.team pairs each id with a teamShortName such as IND or PAK in the example, which gives a compact label for a team selector without a second lookup.
Format ids and selected format filter.matchtype maps matchTypeId to a description (test, odi, t20 in the example) and selectedMatchType reports the format the returned table is for.
Headers with positional rows A headers array names the columns (Batter, M, I, R, SR in the example) and each row is an object holding a values array of strings, so a table can be built from the response alone.
Player id leads every row In the source example each row starts with a numeric string before the player name, which looks like a player id that can be matched against player operations after you verify it.
Text figures to parse Matches, innings, runs and strike rate arrive as strings such as 128.02, so parse them explicitly before sorting and keep the original text if you only display it.

Live API Demo

GET /api/project/cricbuzz-cricket/stats-get-records

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/stats-get-records?key=<API_KEY>&statsType=mostRuns'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the records operation return?

It returns an appIndex object, a filter object with matchtype, selectedMatchType and team entries, a headers array and a values array of player rows, according to the source 200 example. No live probe was recorded, so these fields are not independently verified.

Which parameters does it take?

statsType is required, goes in the query string as a string and defaults to mostRuns. matchType, opponent, team and year are optional numbers in the query string and have no default. No path or body parameters are documented.

Where do I get valid statsType values?

Call the record filters operation of this product and use the value field of the type you want, for example mostRuns, unchanged. Do not guess codes; the supplied evidence documents only the default.

Where do I get team, opponent and matchType ids?

From the filter object in the response of this operation. In the source example filter.matchtype carries matchTypeId strings and filter.team carries id and teamShortName strings. Send those ids as numbers in the matchType, team and opponent query parameters.

How do I read the headers and values arrays?

In the example, headers is Batter, M, I, R, SR and each entry of values holds a values array of six strings. The first looks like a player id, the second is the player name, and the other four follow the M, I, R and SR columns in order, so a row has one more string than headers has entries.

Are the figures numbers or strings?

Strings. Every item in a row, including runs and the decimal strike rate, is delivered as text. Convert them explicitly before sorting or averaging.

Does opponent need team, and what if no records match?

The supplied evidence does not say whether opponent requires team, and it documents only a populated 200 example. Handle an empty or missing table in your client, and test your own combinations of year, team, opponent and matchType.

Is this a series leaderboard or a live ranking?

No. It returns a record table for the chosen statsType and filters. A table limited to one tournament belongs to the series statistics operation, and format-wide player ranks belong to the ranking operations of this product.

Related operations

Guides

View Subscription Plans →