Get a cricket player's batting statistics by playerId as a format-by-metric table, optionally limited to one series with seriesId
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the batting statistics of a single cricket player as a table. playerId is required, goes in the URL path and is a number: use the id value from the trending players or player search operations of this product. The default 8733 is an example value. seriesId is optional, goes in the query string and is a number: pass the id value of a series from the series list or series archive operations to limit the statistics to that series, or leave it empty for the default view. The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a headers array (ROWHEADER, Test, ODI, T20 and IPL in the example), a seriesSpinner array of objects with a seriesName (a single Career entry in the example) and a values array. Each element of values is an object with its own values array of strings: the first string is the metric label and the following strings line up with the format columns in headers. The example metrics are Matches, Innings, Runs, Balls, Highest, Average, SR, Not Out, Fours, Sixes, Ducks, 50s, 100s, 200s, 300s and 400s, and every number is a string. No live probe was recorded for this endpoint, so all fields are source-example fields. The columns, the series options and the defaults when seriesId is supplied are not verified, and career coverage is not guaranteed.
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/players-get-batting API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-batting?key=<API_KEY>&playerId=8733'
Query Result
Use Cases
- Populate a batting statistics tab on a player page, creating one column per entry in headers and one row per metric label in values.
- Compare career numbers with a tournament view by requesting the same playerId once without seriesId and once with a series id, then showing both tables after checking the shape of each response.
- Pivot the values rows into a metric-by-format object and compute a quick average versus strike-rate comparison across Test, ODI and T20 for a scouting note.
- Feed a fantasy research sheet with Runs, Average and SR for shortlisted players found through the trending list, treating them as background statistics and not as points or predictions.
- Build a milestone card that shows the 50s and 100s counts per format for a player-of-the-week feature, hiding any column that the headers do not contain.
Frequently asked questions
What does the batting statistics operation return?
It returns a table-style object: an appIndex object, a headers array of format columns, a seriesSpinner array and a values array of rows. Each row's own values array starts with the metric label followed by one string per column. No live probe was recorded, so these fields come from the source example.
Where do I get the playerId?
Use the id value from the trending players or player search operations of this product. They return it as a string of digits, and this endpoint declares playerId as a required number in the URL path. The default 8733 matches the player in the source example and is only an example value.
What does seriesId do and where do I find it?
seriesId is optional and limits the statistics to one series. Take its id from the series list or series archive operations of this product; the source gives 7607 for IPL 2024. What the response looks like for a given series is not covered by a probe, so inspect headers and values for each series you request.
Why are all the numbers strings?
In the source example every value, including Runs, Average and SR, is a string. Parse them in your client, and keep the original text if you need to preserve the data source's rounding.
Are the columns always Test, ODI, T20 and IPL?
The example shows those four columns after ROWHEADER, but the columns for other players or series are not documented. Read headers on every response and match each metric row to a column by position instead of hard-coding the format names.
What is the seriesSpinner field?
It is an array of objects with a seriesName. The source example contains a single Career entry. Its meaning for series-scoped calls is not verified, so inspect it in your own responses before using it to build a selector.
Does this cover a player's complete career?
Not necessarily. Coverage depends on the data source, and the supplied evidence does not guarantee complete career records or specific competitions. Check the returned Matches and Innings rows before presenting the table as a full career summary.
What are the appIndex fields for?
appIndex holds seoTitle and webURL strings that describe the player's page at the data source. They are metadata about the response, not statistics, so do not mix them into the batting table.