ilovepsxAPI
PAKISTAN MUTUAL FUND DATA

Pakistan mutual fund NAV API

Bring dated mutual fund prices into your application, research notebook, or internal dashboard. Query latest available NAV values and historical series through a consistent REST API.

Free unlimited monthly usageNo card required

Start with a canonical fund

A fund name can appear in different forms across source documents. Begin with the canonical registry, then use the returned fund slug for your NAV requests. The registry lets you search and filter by AMC, category, and Shariah-compliant classification.

Send your API key in the X-API-Key header. You can create separate scoped keys for development and production in your workspace. The current release has no monthly usage quota, usage charges, or payment-card requirement.

Discover funds
curl --header "X-API-Key: $ILOVEPSX_API_KEY" \
  "https://funds.api.ilovepsx.com/v1/mutual-funds/funds?per_page=10"

Query historical NAV values

Use the fund’s returned slug in the historical NAV endpoint. Limit the requested date range, choose the ordering, and follow the returned cursor for additional pages. Replace the placeholder below with a real registry slug; sample dates are illustrative.

Historical NAV query
curl --header "X-API-Key: $ILOVEPSX_API_KEY" \
  "https://funds.api.ilovepsx.com/v1/mutual-funds/funds/FUND_SLUG/nav?from=2026-09-01&to=2026-09-30&limit=100&order=asc"

Preserve financial precision

Financial decimals are returned as JSON strings. Keep them as strings when storing or displaying exact source values, and use decimal arithmetic for calculations. Converting a value straight to a binary floating-point number can change its precision. Charts in the portal use approximate positions while the data tables preserve the original decimal values.

Read the dates before using the price

A latest available NAV is the latest published value in the production dataset. It is not an intraday market quote, a guarantee of same-day publication, or a substitute for the source date. Holidays, delayed publication, and missing source periods can affect a fund’s history.

Check response dates, coverage, and freshness metadata before making comparisons. A missing record does not mean a price of zero. The NAV series also describes a different period from a monthly Fund Manager Report.

Build a reliable integration

  • Store your secret key in a server-side environment variable.
  • Use bounded date ranges and paginate instead of requesting every record at once.
  • Honor burst protection and Retry-After on HTTP 429 responses.
  • Keep response request IDs when diagnosing failed calls.
  • Check coverage before assuming every fund has the same depth of history.

Use the dashboard explorer to inspect real responses before integrating. The API reference documents the latest NAV and historical NAV operations, parameters, and response schemas. The FMR API guide explains how to add monthly report context alongside NAV history.