List the cricket record types (statsType values) accepted by the records operation, grouped into Batting and Bowling with display headers

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

Returns the catalog of record types that the cricket records operation of this product accepts in its statsType parameter. The operation takes no parameters: there is no path, query or body input to set. The source 200 example is an object with a statsTypesList array. Each element has a category string and a types array, and each entry of types has a category string, a header string (the display label, such as Most Runs) and a value string (the machine value to send as statsType, such as mostRuns). The example lists two groups: Batting with nine types (mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties) and Bowling with six types (mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon, lowestSr). The header of bestBowlingInnings is Best Bowling followed by a trailing space in the example, so trim display labels before comparing them. The example contains no team or match type lists; those filters appear in the response of the records operation itself. No live probe was recorded for this endpoint, so every field described here comes from the source example and is not independently verified, and the evidence does not show whether the list changes by season or coverage.

API Features

Parameter-free catalog call The operation needs no path, query or body inputs, so a client can request the full list of record types with a single plain GET at startup.
Batting and Bowling groups statsTypesList splits the types into category groups, with Batting and Bowling in the source example, so a selector can render grouped sections straight from the response.
Value and header pairs Each type carries a machine value such as highestAvg and a human header such as Best Batting Average, which keeps the sent code and the label shown to users in one object.
Values for the records statsType input The value strings are the inputs that the records operation expects in statsType, which removes the need to hard-code or guess record codes in your application.
Fifteen types in the example The source example lists nine batting types and six bowling types, covering run, hundred, boundary, wicket, economy and strike-rate style records.
Category repeated on every type Every type object repeats its own category string, so a flattened list of types still knows whether an entry is a batting or a bowling record.
Label whitespace to clean One header in the example, Best Bowling, ends with a trailing space, a small detail that matters when you match, sort or de-duplicate display labels.

Live API Demo

GET /api/project/cricbuzz-cricket/stats-get-record-filters

No parameters required. Click Query to call the API.

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-record-filters?key=<API_KEY>'
📢
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 record filters operation return?

It returns a statsTypesList array of category groups. Each group has a category string and a types array whose entries hold category, header and value strings, according to the source 200 example. No live probe was recorded, so these fields are not independently verified.

Does it take any parameters?

No. The skeleton for this operation lists no path, query or body parameters, so you send a plain GET request to the operation path and read the list from the response.

How do I use the result with the records operation?

Take the value string of the type you want, for example mostRuns, and pass it unchanged as the required statsType parameter of the records operation of this product. Use the header string only for display.

Does it also return team and match type filters?

Not in the source example, which contains only statsTypesList. The list of team ids and match type ids appears in the filter object of the records operation response, so call that operation to discover valid team, opponent and matchType values.

Which record types appear in the example?

Batting: mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes and mostNineties. Bowling: mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon and lowestSr. Treat the live response as the authority rather than this list.

Why does one header end with a space?

In the source example the header for bestBowlingInnings is Best Bowling followed by a trailing space. Trim display strings in your client before comparing or sorting them. The value string, which is what you send as statsType, has no such space in the example.

Can I assume the list never changes?

The supplied evidence does not say whether the list varies by season, competition or coverage. Cache it for convenience, refresh it periodically, and handle a statsType that has disappeared from the list rather than assuming a fixed set.

Related operations

Guides

View Subscription Plans →