Cricket ball-by-ball deliveries
Stored ball-by-ball for one cricket match. Requires Pro or higher. This is a new capability; the innings scorecard and existing cricket match, series, player and tutorial surfaces remain available on Free. Wides and no-balls are delivery records and remain present as rows. Same-day double-headers can share a canonical match id; when that happens, retry with one of the opaque stream numbers returned in meta.available_streams. Internal source references are never exposed.
Request
- Base URL: https://api.bigballsdata.com
- URL: https://api.bigballsdata.com/v1/cricket/matches/{id}/deliveries
- Auth: one of:
- API key in header x-api-key
- HTTP bearer
Path parameters
A stored BigBalls id. This is the identifier every match, team, player and league endpoint returns, and the one every {id} path segment accepts. Take it from the id field of the corresponding list endpoint and use it as-is.
Query parameters
Opaque one-based stream selector, needed only when the match id represents more than one same-day match.
Exact meta.next_cursor from the previous page. It carries innings, super-over, over and delivery position.
Response
A collision-safe page of stored deliveries.
Example response
{
"meta": {
"date_window": {
"timezone": "UTC",
"start_utc": "2026-09-13T00:00:00.000Z",
"end_utc": "2026-09-14T00:00:00.000Z"
},
"source": "official-league",
"confidence": 0.95,
"cache_age_ms": 4200,
"request_id": "req_abc123",
"note": "match_id is omitted on 380 of 380 rows in this response. The live feed behind them does not carry an id we can resolve to a stored match, so we return no id rather than one that will not work. For rows with ids you can call back into, use /v1/stored/matches with the same sport or league, for example /v1/stored/matches?league=epl."
},
"error": {
"code": "NOT_FOUND"
}
}Changes
No recorded changes to this operation across all 3 revisions of this API.