Deliveries and extras

Every ball bowled is one delivery, in order within its innings. /v1/matches/{match}/deliveries returns them all, and each carries where it sits in the over, who faced it, who bowled it, and what it scored.

Numbering

over is the over the ball belongs to, counting from 1. ball counts the legal balls bowled in that over so far, so a wide or a no-ball does not move it on: an over with a wide in it has seven deliveries but still only six legal balls.

batter faced the ball and partner was at the other end. Deliveries come in the order they were bowled. Use that order to sequence them, rather than rebuilding it from over and ball.

Runs

runs.batter is what the batter scored off the bat, runs.extras what the ball gave away otherwise, and runs.total the two together. Where there were extras, extras names them: wides, no_balls, byes, leg_byes or penalty, each only when it is not zero.

A four or a six that was run rather than hit to the boundary carries all_run: true. The analytical endpoints leave those out of their boundary counts.

Wickets

A ball that took a wicket has a wickets list, almost always of one: how_out (caught, bowled, lbw, run out, stumped and so on), who was dismissed, and who it was fielded_by. A run out can dismiss the partner, the batter at the other end, so always read dismissed rather than assuming the batter.

Players

Names come once, in the players dictionary at the top, keyed by address. Each ball carries only the addresses, which keeps a Test match to a manageable size.

By plan

The free key gets the first over of any match as a sample. Match Week gets every ball of the last 7 days, and Archive and Analyst Pro every ball since December 2001. The response says how many balls were held_back.