POST /api/moneycontrol/mutual_funds
Price: 10 credits
Get an Indian mutual fund scheme from Moneycontrol by scheme id or page URL: NAV and its change, AUM, expense ratio, category, AMC, benchmark, objective, riskometer, fund managers, CAGR, trailing returns with category average and rank, risk ratios, asset and market-cap allocation, valuation against the category, debt-fund yield to maturity, duration, maturity and credit quality, and the scheme's other plan and option variants
aum is in INR crores. Find a scheme id with moneycontrol/mutual_funds/search; moneycontrol/mutual_funds/holdings lists the portfolio.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)fund string required — Moneycontrol mutual fund scheme id or moneycontrol.com scheme page URL (examples: "MPP002", "https://www.moneycontrol.com/mutual-funds/nav/parag-parikh-flexi-cap-fund-direct-plan/MPP002")@type string (default: "MoneycontrolMutualFund")id string requiredisin string nullablemorningstar_id string nullablename string nullableshort_name string nullableurl string nullableis_active boolean nullableis_etf boolean nullableplan string nullableoption string nullablecategory string nullablesub_category string nullableamc string nullableamc_id string nullablebenchmark string nullableobjective string nullableriskometer string nullablelaunch_date integer nullablelock_in string nullableinvestment_style string nullablestar_rating integer nullablenav number nullablenav_change number nullablenav_change_percent number nullablenav_date integer nullableaum number nullableexpense_ratio number nullablecagr_3y number nullablecagr_5y number nullablecagr_7y number nullablecagr_10y number nullablecagr_since_inception number nullablesharpe_ratio number nullablesharpe_ratio_category number nullablestandard_deviation number nullablestandard_deviation_category number nullablebeta_3y number nullablebeta_3y_category number nullableturnover_ratio number nullableturnover_ratio_category number nullabletop_3_sector_weight number nullabletop_5_stock_weight number nullabletop_10_stock_weight number nullableholding_count integer nullableaverage_market_cap string nullableequity_percent number nullabledebt_percent number nullablecash_percent number nullableother_percent number nullablelarge_cap_percent number nullablemid_cap_percent number nullablesmall_cap_percent number nullableother_cap_percent number nullableyield_to_maturity number nullablemodified_duration number nullableaverage_maturity number nullableaverage_credit_quality string nullablecredit_aaa_percent number nullablecredit_aa_percent number nullablecredit_a_percent number nullablefund_managers array (default: [])@type string (default: "MoneycontrolFundManager")name string requiredrole string nullablestart_date integer nullableend_date integer nullablevariants array (default: [])@type string (default: "MoneycontrolFundVariant")id string requiredisin string nullablename string nullableplan string nullableoption string nullablepayout_frequency string nullableurl string nullablereturns array (default: [])@type string (default: "MoneycontrolFundReturn")return_type string requiredperiod string requiredreturn_percent number nullablecategory_average number nullablecategory_rank integer nullablecategory_fund_count integer nullablevaluation array (default: [])@type string (default: "MoneycontrolFundRatio")name string requiredvalue number nullablecategory_average number nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Moneycontrol has no mutual fund scheme under that id Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.