Monthly reports provide a different kind of context
Daily NAV values describe dated fund prices. A Fund Manager Report describes a monthly reporting period and may contain profile, performance, and portfolio sections. Treat these as different datasets rather than assuming a report reflects today’s NAV or holdings.
The ILovePSX FMR API serves safely promoted production facts. Extracted source output goes through deterministic validation, staging, fund matching and safe promotion before it reaches public endpoints. The customer explorer reads those production facts; it does not expose raw AI extraction or private review controls.
Find the fund, then request its report
Use the canonical registry to obtain the fund slug. The latest report endpoint returns the latest available production report, while dated operations let you request a reporting period explicitly. Replace the placeholder in this example with a slug returned by the registry.
curl --header "X-API-Key: $ILOVEPSX_API_KEY" \ "https://funds.api.ilovepsx.com/v1/mutual-funds/funds/FUND_SLUG/fmr-reports/latest?include=all"
Work with the sections the source provides
Source reports differ in format and coverage. Available structured sections can describe the fund profile, performance, asset allocation, holdings, and fees. Not every source report publishes every field, and not every fund has a promoted report for every month.
Review the public endpoint schemas for supported sections and parameters. Financial decimals remain strings to preserve precision. Values can be null or absent when source facts are missing; a blank field is not a reported zero.
Use coverage to avoid silent assumptions
Check production coverage and the report date before building a comparison, dashboard, or research table. Keep the source and reporting-period context when supplied by the API. If a requested period is unavailable, handle that state visibly in your application rather than silently substituting a different month.
The portal explorer provides readable and JSON views so you can inspect a fund’s available reports. It also distinguishes report dates from the date range used for historical NAV queries.
Free access, with a secure integration
FMR reads are included in the current free release, with unlimited monthly usage and no card requirement. Complete report reads use two activity units for burst protection; these units are workload measures, not a usage bill. Pagination, request bounds, and security controls remain in place.
Keep your API key on your server, select the read scopes your application needs, and rotate or revoke a compromised key. The integration guide covers authentication, errors, and response conventions. These datasets support research and product development; they do not provide investment advice or guarantee fund performance.