Mutual Fund Fee Data

API Overview

This API provides detailed fee rate data query services based on the fund code (fundCode). The returned content covers tiered details for fund subscription rates (subscribeRate), purchase rates (purchaeRate), and redemption rates (redeemRate), as well as fixed fee indicators such as fund management fees, custody fees, and sales service fees. It also provides transaction rule data such as buy/sell confirmation days, regular investment status, and minimum subscription/redemption amounts, helping developers build a transparent fund transaction display layer.

Use Cases

• Financial Wealth Management Apps: Display precise transaction costs on fund detail pages, including redemption rates for different holding periods and subscription discounts for various amounts.
• Investment Advisory Analysis Systems: Calculate the comprehensive fee cost of fund holdings to assist users in long-term return estimation.
• Fund Comparison Tools: Compare management fees, custody fees, and transaction thresholds of different funds for decision support.
• Automated Trading Systems: Verify whether trading instructions comply with minimum subscription amounts, daily limits, and lock-up period restrictions.

Request and Response Details

• Request Method: POST
• Core Parameters: fundCode (string, required), the standard 6-digit fund code.
• Response Data:
• data.purchaeRate / data.redeemRate: JSON string format, containing specific fee rate values corresponding to amount ranges or holding periods.
• data.trusteeRate / data.serviceRate: Annualized fund management fee and custody fee, respectively.
• data.minPurchase / data.minRedeem: Minimum subscription and redemption amounts.
• data.purchaeComfirmDay / data.redeemComfirmDay: Number of working days required for transaction confirmation.
• data.regularStatus: Indicates whether the fund has enabled regular investment (1 for enabled, 0 for disabled).

Integration Suggestions

1. Data Parsing: Fee-related fields (e.g., purchaeRate) are typically returned as JSON strings; frontend or backend processing is required for secondary parsing to render tiered fee tables.
2. Caching Strategy: Fund fee rates are adjusted infrequently; it is recommended to cache query results appropriately (e.g., 24 hours) to reduce API call frequency and improve response speed.
3. Error Handling: Handle cases where the fund code does not exist or the fund has been liquidated. Check if the returned code is 200 and pay attention to the msg for error prompts.
4. Compliance Display: When displaying fee rates, please retain the precision of the original data and state 'Fees are for reference only; subject to the latest announcement from the fund company' to avoid compliance risks.