OPEN DATA

Free Cricket API: What Open Ball-by-Ball Data Can and Cannot Do

Cricsheet publishes ball-by-ball data for tens of thousands of matches under an open licence. That makes a free cricket API possible. It also sets clear limits, and an honest API should say what they are.

What open data covers well

The archive starts in 2001 and includes men's and women's Tests, ODIs and T20Is, ICC events, associate nations and the major T20 leagues. Every match has deliveries, players with registry IDs, officials, toss and result.

  • Ball-by-ball deliveries with extras, wickets and fielders.
  • Stable person identifiers across all matches.
  • Women's cricket alongside men's cricket.
  • Associate nations such as Nepal, Namibia, Scotland and Rwanda.

What it does not include

Open data records what happened to each ball, not where it went. There are no shot directions, pitch maps or fielding positions. Any wagon wheel built on this data would be invented, so OpenCricket does not draw one.

The data is published after matches finish, so it is not a live feed. Cricsheet also withholds matches that feature the Afghanistan men's team or that were played in the Afghanistan Premier League, as a matter of policy.

Attribution

Cricsheet data is released under the Open Data Commons Attribution License. You can use it commercially if you credit the source. OpenCricket puts the source and licence in the meta block of every response, so attribution travels with the data.

Frequently asked questions

Can I use open cricket data in a paid app?

Yes, under the attribution licence, provided you credit Cricsheet. Check the licence text on cricsheet.org for the exact terms.

Sources and further reading

Product descriptions and examples were checked against the OpenCricketAPI v1 contract on 5 October 2026.