Get cricket statistics for one venue by venueId: matches played, wins batting or bowling first, average scores and highest and lowest totals as key and value pairs
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns a summary of historical statistics for one cricket venue. Send venueId in the URL path (required number; the default 24 is the documented example value). The id comes from the id field returned by the series venues operation of this product. The source 200 example is an object with a venueStats array of key and value string objects, eight entries in total: Total Matches (48), Matches won batting first (7), Matches won bowling first (19), Avg. scores recorded (a multi-line string, 1st inns-310, 2nd inns-337, 3rd inns-261 and 4th inns-159 separated by newline characters), Highest total recorded (765/6(248.5) by PAK vs SL), Lowest total recorded (80/10(53.1) by AUS vs PAK), Highest score chased (315/9(106.1) by PAK vs AUS) and Lowest score defended (149/10(47.1) by SL vs PAK). Every value is text, including counts and scores, and the total and result counts in the example are not guaranteed to add up, so do not derive percentages without checking. The evidence does not say which venue the example belongs to, which match formats are counted, or how the list changes for other venues. No live probe was recorded, so every response field described here comes from the source example and is not independently verified. These are historical figures, not a pitch report, weather feed or forecast.
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/venues-get-stats API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/venues-get-stats?key=<API_KEY>&venueId=24'
Query Result
Use Cases
- Add a venue statistics tab to the information page of a selected cricket ground, rendered directly from the key and value pairs.
- Show a pre-match context card comparing wins batting first with wins bowling first at the ground, labelled clearly as historical results.
- Build a comparison table across all grounds of a tournament by looping over the ids returned by the series venues operation and requesting each venue once.
- Quote the highest score chased and the lowest score defended in an editorial preview, after splitting the text into score, overs and teams in your own code.
- Store parsed venue totals in a research dataset, splitting the average-score string on newline characters to get one number per innings.
Frequently asked questions
What does the venue statistics operation return?
It returns an object with a venueStats array. Each entry is an object with key and value strings, such as Total Matches, Matches won batting first or Highest total recorded, according to the source 200 example. No live probe was recorded, so these fields are not independently verified.
Which parameter does it take?
venueId only. It is required, goes in the URL path as a number and defaults to 24, the documented example value. No query or body parameters are documented.
Where do I get a venueId?
Use the id field returned by the series venues operation of this product, which lists the grounds of a series. Pass that id unchanged in the path.
How is the average score entry formatted?
In the source example it is one string with four lines, 1st inns-310, 2nd inns-337, 3rd inns-261 and 4th inns-159, separated by newline characters. Split on newlines and then on the hyphen to get one figure per innings.
Are the values numbers or text?
Text. Counts such as 48 and totals such as 765/6(248.5) by PAK vs SL are all strings. Parse the numbers in your own code and keep the original text when you only need to display it.
Can I compute win percentages from the counts?
Be careful. In the example, the batting-first and bowling-first win counts do not add up to Total Matches, and the evidence does not explain the difference. Show the counts as returned unless you have verified what the remaining matches represent.
Is this a pitch report or weather forecast?
No. The entries are historical venue figures. The operation does not return pitch condition, weather or a prediction of scoring in a future match; use the venue and pitch research operation of this product for match-level ground notes.
Which formats and years are counted?
The supplied evidence does not say. It documents one populated 200 example without a venue name, format or date range, so verify the scope of the figures for your own venues before publishing them.