Built and run by one person.
Pulling Tigzig Data Through the API? There Is a Second Way In. The Whole Database Is Published for Download.
Top•MFPRO - Mutual Fund Analytics•TREMOR - Macro Stress Signals•VIGIL - India Red Flag Events

Pulling Tigzig Data Through the API? There Is a Second Way In. The Whole Database Is Published for Download.

Published: August 31, 2026

Related toolsMFPRO - Mutual Fund Analytics•TREMOR - Macro Stress Signals•VIGIL - India Red Flag Events

If you are an analyst or a tool builder pulling Tigzig data through the API, there is a second way in. The whole database is published for download. Build your own micro-service, analyze it offline, or have your agent dig into it.

The dataset is refreshed back to back with the live one, and comes with a manifest with the generation timestamp on it, so you can see how current your copy is. Take a single table as parquet or CSV, or take the lot as one DuckDB or SQLite file.

API or download? Sometimes the API is the right tool, and your API calls are welcome. In other cases, pulling the whole thing down and putting your own microservice in front of it gives you the same data without the API dependency and constraints.

Tip. If you have a Claude subscription it comes with Cowork, which comes with a python enabled sandbox installed on your local machine. It can download and analyze all the Tigzig data without breaking a sweat.

Free, no signup, no API key.

What is in each

Mutual funds. NAV master from AMFI data, every scheme, going back to 2006. 37 million records.

Cricket. Ball by ball for men's Tests, ODIs and T20 internationals, 6,900+ matches from 2001, 3.8 million deliveries.

Global macros. 300+ indicator series across the US, India, Europe and the OECD.

India red flag. Related party transactions, insider trading, pledges, credit ratings and surveillance.

Every one is available table by table if you only want a slice, or as a single file with everything in it.

tigzig.com/apis

If you are going to schedule this rather than pull it by hand

Read the manifest first. Every dataset publishes one at /downloads/manifest, and it gives you the generation timestamp, the size of each file and the row counts, so a scheduled job can check the stamp and skip the download when nothing has changed.

That timestamp answers the question "is this stale". If it looks old, my live data is equally old and I am already looking at it, because the sync pipeline is monitored end to end.

And if you would rather not read any of it, point your agent at api.tigzig.com and ask for the dataset you want.

The whole Tigzig database, published for download

Working on something similar? How I work covers the rates, the availability and what I take on.