Built and run by one person.
Women's Cricket Is Now in the Cricket Database. Four New Tables, 2,774 Matches and 850K+ Deliveries Back to 2003.

Women's Cricket Is Now in the Cricket Database. Four New Tables, 2,774 Matches and 850K+ Deliveries Back to 2003.

Published: September 3, 2026

Women's cricket is now in the cricket database. Four new tables covering Test, ODI and T20 ball by ball, 2,774 matches and about 850K+ deliveries going back to 2003. It is queryable live, via API and MCP, and it is in the bulk download.

That takes the whole thing to 9,700+ matches and 4.7 million+ deliveries across eight tables, refreshed twice daily.

The women's data sits in its own four tables.

You can take the whole database as a download, about 12 MB as DuckDB or 83 MB as SQLite, or one table at a time as CSV or parquet, or query it live with SQL on Postgres and DuckDB. Plus there is an MCP endpoint an agent can use directly.

Free, no signup, no API key.

Downloading the full database

You can download via the API or do it manually at tigzig.com/apis/database

Scheduled jobs. If you are going to schedule this rather than pull it by hand, read the manifest first. It sits at api.tigzig.com/cricket/v1/downloads/manifest and carries the row count and the size for every file plus a generated_at stamp, so a job can check whether anything has changed before it downloads anything.

Conditional requests. The files answer conditional requests as well. Send If-None-Match with the ETag you got last time and you get back a 304 with no body when nothing has changed. A matching ETag returns 304 and zero bytes, a bogus one returns the full file. The rebuild runs twice a day, so a job polling more often than that is pulling the same bytes over and over, and that one header removes all of it.

What is in the women's tables

Of the 2,774 women's matches, T20 is most of it, 2,141 matches from 2009 onwards, then 609 ODIs from 2007, and Test is 24 matches going back to 2003.

The ball-by-ball tables carry no gender column, which is why the women's data is in separate tables.

Players are identified by name string and there is no stable player id currently in the data, so joining this to another source means matching on names.

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.

The cricket dataset linked here is from Cricsheet, published under the Open Data Commons Attribution License 1.0 (ODC-BY). If you redistribute it, keep the attribution and the licence with it.