Mutual Fund Insights

This API returns mutual fund holdings aggregated at the folio level. Each holding includes AMC name, scheme code, ISIN, NAV, units, current value, cost value, and a per-folio breakdown with individual folio numbers, units, and values.

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

→ filterCdslNsdl (optional): Set to "true" to filter out CDSL/NSDL demat-held mutual fund folios. Default: "true".

→ filterZeroValueAccounts (optional): Set to "true" to exclude accounts with zero balance. Default: "false".

→ filterZeroValueHoldings (optional): Set to "true" to exclude holdings with zero value. Default: "false".

This API returns all linked Mutual Fund accounts for a user, grouped by FIP (Financial Information Provider). Each linked account includes AMC, folio number, holder info (name, PAN, DOB, email, mobile), consent status, holdings count, and current/cost values.

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

→ filterCdslNsdl (optional): Set to "true" to filter out CDSL/NSDL demat-held mutual fund folios. Default: "true".

→ filterZeroValueAccounts (optional): Set to "true" to exclude accounts with zero balance. Default: "false".

→ filterZeroValueHoldings (optional): Set to "true" to exclude holdings with zero value. Default: "false".

This API retrieves the user's subscription status along with a summary of all Mutual Fund FI data. It shows subscription start/end dates and a per-FIP account breakdown.

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

This API returns the transaction history for mutual fund accounts. Each transaction includes ISIN, AMC, NAV, units, amount, folio number, tax details, and more. You can filter by specific ISIN, folio, broker, or date range.

Prerequisites:

→ First call POST mutual-fund/user-linked-accounts to get the list of linked mutual fund accounts.

→ From the response, pick the fiDataId of the desired account.

→ Pass that fiDataId as the "accountId" parameter in this API.

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

→ accountId (required): The fiDataId of the specific account.

→ dateRangeFrom (optional): Start date for filtering transactions. Format: yyyy-MM-dd.

→ dateRangeTo (optional): End date for filtering transactions. Format: yyyy-MM-dd.

→ txnOrder (optional): Sort order — "ASC" (oldest first) or "DESC" (newest first). Default: "ASC".

→ brokerId (optional): Filter transactions by specific broker ID.

→ folioNo (optional): Filter transactions by specific folio number.

→ isin (optional): Filter transactions by specific ISIN code.

→ isins (optional): Filter transactions by multiple ISIN codes (array of strings).

→ accountIds (optional): Filter transactions by multiple account IDs (array of strings).

→ maskedFolioNos (optional): Filter transactions by masked folio numbers (array of strings).

→ filterCdslNsdl (optional): Set to "true" to filter out CDSL/NSDL demat-held mutual fund folios. Default: "True".

This API returns portfolio-level mutual fund insights WITHOUT any Personally Identifiable Information (PII). The response includes an overall summary with current value, invested value, absolute return, XIRR, daily returns, plus distribution breakdowns by category, sub-category, market cap, AMC, and sector. Per-holding insights include fund name, ISIN, returns, NAV, units, and SIP info.

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

→ filterZeroValueAccounts (optional): Set to "true" to exclude accounts with zero balance. Default: "false".

→ filterZeroValueHoldings (optional): Set to "true" to exclude holdings with zero value. Default: "false".

This API returns full mutual fund insights WITH PII (Personally Identifiable Information). The response includes the overall summary (PAN, mobile, total holdings, current value, invested value, absolute return, XIRR, daily returns) and per-holding breakdown with benchmark comparison, per-folio insights, and distribution data.

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

→ filterZeroValueAccounts (optional): Set to "true" to exclude accounts with zero balance. Default: "false".

→ filterZeroValueHoldings (optional): Set to "true" to exclude holdings with zero value. Default: "false".

This API returns mutual fund analysis with scheme category and scheme type distribution. It shows current value, cost value, total holdings, and how holdings are distributed across different scheme categories (e.g., Equity, Debt, Hybrid) and scheme types (e.g., Open-Ended, Close-Ended).

Request Body Parameters:

→ uniqueIdentifier (required): The primary identifier added at the time of subscription. It must be the exact same value used during the initial subscription and MUST never change for this user.

→ filterCdslNsdl (optional): Set to "true" to filter out CDSL/NSDL demat-held mutual fund folios. Default: "true".

→ filterZeroValueAccounts (optional): Set to "true" to exclude accounts with zero balance. Default: "false".

→ filterZeroValueHoldings (optional): Set to "true" to exclude holdings with zero value. Default: "false".

This API compares mutual fund benchmark trailing returns across configurable time ranges. It shows how a benchmark index performed over a trailing period (e.g., last 1 month) starting from a given date. This helps users see how their mutual fund returns compare against market benchmarks.

Request Body Parameters:

→ benchmarks (required): The benchmark code/ID to compare against (e.g., "OB48").

This is a Wealthsync internal code for a specific benchmark index (e.g., Nifty 50, Sensex, etc.).

You can pass one or multiple comma-separated codes.

→ from (required): The starting date from which trailing returns should be calculated. Format: yyyy-MM-dd.

→ ranges (required): The trailing return period.

Supported values: "1D" (1 day), "1W" (1 week), "1M" (1 month), "3M" (3 months), "6M" (6 months),

"1Y" (1 year), "3Y" (3 years), "5Y" (5 years), etc.

You can pass multiple comma-separated ranges like "1M,3M,1Y".

Example: { "benchmarks": "OB48", "from": "2024-02-01", "ranges": "1M" } This means: "Show me the trailing 1-month return of benchmark OB48 starting from February 1, 2024."

This API compares mutual fund benchmark returns between two specific date points. It shows how a benchmark index performed from one specific date to another.

Request Body Parameters:

→ benchmarks (required): The benchmark code/ID to compare against (e.g., "OB48").

This is a Wealthsync internal code for a specific benchmark index.

You can pass one or multiple comma-separated codes.

→ point_1 (required): The start date for the comparison period. Format: yyyy-MM-dd.

→ point_2 (required): The end date for the comparison period. Format: yyyy-MM-dd.

Example: { "benchmarks": "OB48", "point_1": "2024-01-01", "point_2": "2024-06-01" } This means: "Show me how benchmark OB48 performed between January 1, 2024 and June 1, 2024."