Mutual fund data API: endpoints, keys and plans

What the API is for

Most free Indian mutual fund data is either a raw NAV file or a web page. The first has no computed returns; the second is not built to be read by a program. The WealthTicker API sits between them. It serves the AMFI scheme universe, daily NAV history and the return and risk figures the site computes, over plain keyed JSON endpoints. It is for developers building a portfolio tracker, a spreadsheet, a newsletter or a research notebook.

Everything below is as the developers page states it on 16 October 2026, with one worked example run on data to 15 October.

Step 1: get a key

Sign in with a free account and open Settings → API keys. Keys start with wt_live_, are shown once at creation and stored hashed. A lost key is revoked and replaced, not recovered. You can hold up to five active keys, and they all draw on one account allowance. Send the key in an X-Api-Key header; Authorization: Bearer works too.

Step 2: know the endpoints

All paths sit under https://wealthticker.in/api/v1:

/funds runs the same engine as the site's screener. It takes plain filters (category, amc, plan, option, minAum, maxExpenseRatio, codes) or a query expression in q, written exactly as in the query builder. Results sort on any of about 30 columns and page up to 500 rows at a time.

A worked example

Suppose you want the cheapest large index funds by 5-year return:

curl -G -H "X-Api-Key: $WT_KEY" "https://wealthticker.in/api/v1/funds" \
  --data-urlencode "q=sub category = Index Funds AND expense ratio < 0.2 AND aum > 1000" \
  -d plan=Direct -d option=Growth -d sort=ret5y -d dir=desc -d limit=3

On data to 15 October 2026 this matched 16 funds (meta.total). The first three by 5-year CAGR:

1. Bandhan Nifty 50 Index Fund (code 118482): 5.70%, expense ratio 0.16%
2. Navi Nifty 50 Index Fund (149039): 5.67%, expense ratio 0.10%
3. Nippon India Index Fund, Nifty 50 Plan (118741): 5.65%, expense ratio 0.15%

Each row is a full fund object, so no second call is needed. To refresh one known fund, call /funds/120716 for UTI Nifty 50 Index Fund. On 15 October that returned latestNav 161.9479, expenseRatio 0.25, rating 3, returns.y1 −8.3589, returns.y10 11.4045 and risk.maxDrawdown −38.4179, with benchmark "Nifty 50 TRI". The same numbers appear on the fund's page, because both read the same computed row.

Three conventions catch people out:

• aum in a response is in rupees: 292847871000 is ₹29,284.8 crore. But aum inside q, and minAum, are in crore.
• returns.m1, m3, m6 and ytd are absolute; y1 and longer are CAGR. Every trailing return turns null once a fund's latest NAV is more than 15 days old.
• ETFs and side-pocketed schemes are left out of /funds unless you ask for category=ETF or list codes.

Step 3: pick a plan

The developers page lists three plans:

Limits are per account, per calendar day in IST, with the monthly ceiling on top. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Past the daily limit you get a 429 rate_limited with a Retry-After header; past the monthly one, a 429 monthly_limit. A request refused for quota still counts.

The free plan's NAV history is the trailing year, measured back from the fund's own latest NAV; meta.truncated says when older points were cut. Direct plans start no earlier than January 2013, when they were introduced.

What the API does not do

It does not give advice, and the terms say the data comes without warranty of accuracy or timeliness. NAVs and scheme data come from AMFI's public feeds and holdings from the AMCs' monthly disclosures; the computed metrics are the site's own, with formulas on the methodology page. Use in your own product is allowed with attribution, but bulk raw dumps may not be resold as a competing feed. Only /api/v1/* is a stable, versioned surface.

For a sense of what the computed fields look like in use, comparing low-volatility and quality index funds and Nifty 500 and total market index funds compared are built from the same figures. The index funds guide explains why expense ratio and tracking matter most for this kind of fund. Every endpoint, with a sample request and response, is on the developers page.