Search Indian mutual fund schemes by name and get the scheme id, ISIN, scheme type and category id of each match.
View all Indian Stock Exchange API endpoints →Searches Indian mutual fund schemes with one required free-text query parameter, for example nippon, and returns a JSON array of matching schemes. Each documented item carries id (an internal scheme identifier such as MF000063), schemeName (the full plan name, including the plan variant such as Direct Plan - Growth Option or Payout Income Dist cum Cap Wdrl), isin (for example INF204KA1W02), schemeType (the sample shows Open Ended Investment Company) and categoryId (a category code such as MFCAT002 or MFCAT003). These fields come from the published documentation and a stored sample response for query=nippon; no live probe of this endpoint has been run in this catalog, so the matching rules for multi-word queries, the result cap and the ordering are unverified. The endpoint identifies schemes only. It returns no NAV, returns or ratings, which the mutual funds listing endpoint provides by fund name.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/indian-stock-exchange-api/mutual-fund-search API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/mutual-fund-search?key=<API_KEY>&query=nippon'
Query Result
Use Cases
- Power a scheme-picker typeahead that shows the ISIN and scheme type beside every suggested fund name.
- Map free-text fund names parsed from a broker or account statement PDF to ISINs before importing holdings into a portfolio tracker.
- Build an ELSS directory page by running a tax-saver query and listing every plan the search returns with its ISIN.
- Group the direct, payout, growth and dividend-reinvestment names of one fund family into a single card by parsing schemeName.
Frequently asked questions
What does the query parameter accept?
query is required and takes a free-text fragment of a scheme name. The documented default is nippon, and the sample response for it lists schemes whose names start with Nippon India. How multi-word queries, ISIN strings and letter case are handled is not stated in the evidence, so test your own search terms before relying on them.
Which fields does each search result contain?
Each array item has id (for example MF000063), schemeName, isin (for example INF204KA1W02), schemeType (Open Ended Investment Company in the sample) and categoryId (for example MFCAT002). These come from the documented example and a stored sample response rather than a live verification.
Why do I get several rows for what looks like the same fund?
Each plan variant is a separate scheme with its own id and ISIN. In the sample, Nippon India Equity Savings Direct Growth (INF204KA1W77) and Nippon India Equity Savings Direct Bonus (INF204KA1W85) are different entries, as are the payout and quarterly payout names. Group them yourself by parsing schemeName.
Does this endpoint return NAV or returns?
No. It returns scheme identity only. Latest NAV, percentage change and 1 month to 5 year returns are served by the mutual funds listing endpoint, whose entries carry fund_name but no ISIN or id, so joining the two needs name matching.
What does categoryId stand for?
It is a category code such as MFCAT002 or MFCAT003. In the sample, equity savings and hybrid schemes share MFCAT002, while ELSS tax saver and multi cap schemes share MFCAT003, but no label table is returned, so treat it as an opaque grouping key.
Is the result suitable for trading or official records?
Treat it as an informational lookup. It helps you find a scheme and its ISIN, but confirm the scheme details with the fund house or the exchange before using them in an order or a regulatory filing.