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
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/stats-get-record-filters No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/stats-get-record-filters?key=<API_KEY>'
Query Result
Use Cases
- Populate a record-type dropdown in a cricket records explorer from the value and header pairs instead of hard-coding statsType strings.
- Render grouped Batting and Bowling sections in a mobile record picker by iterating statsTypesList and its types arrays.
- Validate a saved or user-typed statsType against the returned value strings before sending a records request, so a typo such as mostRun is caught on the client.
- Cache the catalog when an app starts and refresh it on a schedule so that newly added or removed record types show up without a code release.
- Generate a glossary page that maps codes like lowestEcon and bestBowlingInnings to their display headers for editors and support staff.
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.