Get cricket runs-per-over graph data by match ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns runs-per-over graph data for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series, team schedule and result, and venue match endpoints. There are no query parameters, so no innings, over-range or team filter can be sent; one request targets one match. No probe call was recorded for this operation, and the only source response example is an empty JSON object (`{}`), so this operation has no documented response fields: no over numbers, run totals, innings keys or team identifiers are confirmed here. Treat the output shape as unverified, inspect a live response for the match you care about, and only then bind it to a chart or table. The payload is intended as aggregated over-level data, which is a different view from the delivery-level data in the over-details and commentary operations of the match-details group. Coverage depends on the competition and match state, so an empty or minimal body is a plausible result for fixtures that have no graph data yet or never had any.
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/match-details-get-overs-graph API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-overs-graph?key=<API_KEY>&matchId=41881'
Query Result
Use Cases
- Supply a runs-per-over comparison component for a selected match after checking the returned graph-data schema against a live response.
- Export the available over-level series for innings tempo analysis, keeping it distinct from delivery-level commentary.
- Feed a runs-by-over chart panel placed beside the scorecard on a match-center page once the series shape is confirmed.
- Run an editorial pre-publish check that flags matches whose graph payload comes back empty, so a chart module is not published with nothing to draw.
- Prefetch the graph for a finished fixture when a post-match report template needs an over-by-over visual.
Frequently asked questions
What does the overs graph operation return?
It is described as runs-per-over graph data for one match. The only source response example is an empty JSON object and no probe call was recorded, so the field names, nesting and innings handling are not documented. Check a live response before building on it.
Which parameter is required and where does matchId come from?
Only the numeric matchId path parameter is required (default 41881). Use the matchId returned by the match list, schedule, series matches, team schedule and result, and venue match endpoints.
Is the response verified by a probe call?
No. No probe call was recorded for this operation, and the source example is `{}`. Anything beyond the request shape is unverified until you test it against a real match.
How is this different from the over-details and commentary operations?
This operation targets aggregated runs-per-over graph data. The over-details and commentary operations in the match-details group are the place to look for delivery-level information, so do not expect ball-by-ball records here.
Can I filter by innings or over range?
No. The only input is matchId and no query parameters are defined. If the response carries several innings, any selection has to happen on your side after you have inspected the real payload.
Will every match return graph data?
Not necessarily. Coverage is competition and match dependent, and an empty or minimal body is possible for upcoming fixtures or matches without graph data. Handle that case without raising an error in your UI.