Get ball-by-ball graph data for an innings

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

Returns ball-level graph data for one innings of a cricket match. The required numeric `matchId` path parameter selects the match (default 41881) and the optional numeric `iid` query parameter selects the innings (for example 1, default 1). No probe call was recorded for this operation, so the fields below come from a source response example and are unverified. That example is an object with a `balls` array, one entry per delivery, each with ballLabel (a short label such as a run count, W for a wicket or a dot for a dot ball), ballNbr, overNum (for example 49.6), inningsId, totalRuns, event (values seen include NONE, WICKET, FOUR and SIX, sometimes combined with over-break in a comma-separated string), batsmanStrikerId, bowlerStrikerId and an epoch-millisecond timestamp. In the example the newest delivery comes first. The payload holds compact delivery records with player ids only, so it is not a commentary feed or a full event ledger, and the actual series structure should be validated before building charts on it.

API Features

Innings-scoped delivery list The iid query parameter picks the innings, so one matchId can be queried once per innings to get the balls bowled in that innings.
Per-ball event tags The event field marks deliveries such as WICKET, FOUR and SIX, with an over-break tag on the last ball of an over, which makes highlight markers easy to derive.
Chart-ready ball labels ballLabel gives a short symbol for each delivery (runs, W for a wicket, a dot for no run) alongside totalRuns, so a run timeline can be drawn without extra parsing.
Striker and bowler ids batsmanStrikerId and bowlerStrikerId reference players by id, ready to be joined with player or scorecard data for batter and bowler views.
Sequence and time markers ballNbr, overNum and an epoch-millisecond timestamp place every delivery in order and in time, which supports pacing and over-by-over analysis.

Live API Demo

GET /api/project/cricbuzz-cricket/match-details-get-balls-graph

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/match-details-get-balls-graph?key=<API_KEY>&matchId=41881&iid=1'
📢
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 iid parameter mean?

iid is the innings id, for example 1 for the first innings. It is optional and the default is 1. Call the endpoint again with another iid to get a different innings of the same match.

Is this commentary text?

No. The source example contains compact ball records with ids, labels, runs and timestamps, but no commentary text and no player names. Resolve player ids through other player or scorecard endpoints.

In what order are the balls returned?

In the source example the newest delivery comes first, with ballNbr counting down from 300. This was not confirmed by a probe call, so sort by ballNbr or overNum in your own code if order matters.

Which values can the event field take?

The example shows NONE, WICKET, FOUR and SIX, and an over-break tag that can be joined with another value by a comma. Treat the list as open and handle unknown values gracefully.

Can the response be empty?

Yes. Ball-level data depends on coverage, so a match without ball data or an innings that was not played can return no balls. Check that the balls array exists and has entries before drawing a graph.

Related operations

Guides

View Subscription Plans →