Back From Sunday Cricket? Some Cricket SQL Now: A Free Ball-by-Ball Database on DuckDB, Postgres or One Download
Published: October 25, 2026
Paste this into your AI agent: "Go to tigzig.com and let me know what cricket data is available and how to access it."
It will find a ball by ball cricket database that takes your SQL on DuckDB or Postgres, or comes down in one download.
What can you run? Death overs, how chases went, the tight bowling spells, opening stands, and screens that stack several conditions together.
Free, no signup, no API key.
For you: tigzig.com/apis/database
What is in the database, in short
ball_by_ball: one row per delivery, with the batter, the bowler, the runs, the extras and how each wicket fell.
match_info: one row per match, with the venue, the toss, the result and the margin.
match_players: the playing XI and the officials for each match.
people: the player registry, with ESPN Cricinfo IDs for joining to other sources.
One thing to note. team1 and team2 follow the order the sides are listed in, and they do not tell you who batted first. For batting order use the margin columns: winner_runs is filled when the side batting first won, and winner_wickets when the side batting second won. Rain-adjusted D/L results can break that, so check the method column too.
Earlier posts that save time on this database
The 14 things that trip people up: tigzig.com/post/cricket-database-14-things-that-trip-people-up-sep2026
The SQL functions you can use, and the limits to know about: tigzig.com/post/cricket-sql-stats-functions-and-limits-sep2026
When an error keeps coming back, the response body usually names the fix: tigzig.com/post/tigzig-api-error-hints-read-the-body-sep2026
Credit and compliance
Data source is Cricsheet (cricsheet.org), licensed ODC-BY 1.0. TigZig is not affiliated with or endorsed by Cricsheet.
Working on something similar? How I work covers the rates, the availability and what I take on.