Heavy User of the Mutual Fund NAV API? Run Your Own NAV Service Inside Your Own Setup
Published: September 11, 2026
If you are a heavy user of the Tigzig mutual fund NAV API, here is another option. You can run your own NAV service inside your own setup, blazing fast.
The whole dataset is published in multiple formats. The Parquet one is just about 169 MB, with every scheme and every NAV date I hold, going back to April 2006.
There are numerous options depending on your stack. On a Python backend you need one package, duckdb, and it queries the Parquet file directly where it sits. There is no database server to install, no hassles. And Polars also reads the same file just as happily.
Depending on your architecture, if you are querying a file on the same container or same network it would be pretty fast.
To keep your database version current, point a cron at the manifest, which is a small JSON file listing every download with its size, its row count and the time it was built. If the build time has moved since your last run, pull the file again.
Free, no signup, no API key.
A few useful links, as quick reference
API hub tigzig.com/apis/mf-nav
Live tool, MFPRO tigzig.com/mfpro
Data dictionary and how the data is built In MFPRO, under Docs
Guides
- Tigzig API errors, a practical guide
- MF NAV API, the 429 rate limit
- Read the body, not the status code
- MFPRO search filters, 12 fields
SIF, full data download sif.tigzig.com
ISIN checker isin.tigzig.com
Working on something similar? How I work covers the rates, the availability and what I take on.