Built and run by one person.
IPL Ball by Ball Data Arrives on the Tigzig Cricket API This Sunday, 6 September, at 9 am IST. About 1,200 Matches and Every Season Since 2008.

IPL Ball by Ball Data Arrives on the Tigzig Cricket API This Sunday, 6 September, at 9 am IST. About 1,200 Matches and Every Season Since 2008.

Published: September 4, 2026

IPL ball by ball data arrives on the Tigzig cricket API & Manual Download this Sunday, 6 September, at 9 am IST. You query it with SQL, on Postgres or DuckDB, and the whole database is also there as a download if you would rather work with it locally. Free, no signup, no API key.

That adds about 1,200 matches and every season since 2008 to what is already there, which is Test, ODI and T20 for both men and women, roughly 9,700 matches and 4.7 million deliveries going back to 2001.

tigzig.com/apis/database

What is in it, and how the two halves join

There are two halves to it, and they join on match_id.

The ball by ball tables are one row per delivery, so the innings and the over, the striker, the non striker and the bowler, runs off the bat, extras split into wides, noballs, byes and legbyes, and the wicket type and who was out.

Match info is the context around each game, 45 fields, so both teams, venue and city, season and event, the toss and what was chosen, the result by runs or by wickets, player of the match, the umpires and the match referee.

Beyond a scorecard you can do powerplay and death over splits, strike rate and bowling economy, whether the toss call worked out, how a chase finished with balls to spare.

tigzig.com/apis/database

Compliance note

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.