# Look up scheme NAVs

Returns the NAV of one scheme you may sell, by its scheme code. Without `nav_date`, the scheme's latest NAV is returned.
Glomo pulls NAVs from the fund's registrar on a schedule. If this scheme's NAVs were not pulled in the last 24 hours, this request pulls them first, so it can take a few seconds longer. If the registrar cannot be reached, you get the NAVs Glomo already has. Check `nav_date` to see how recent each one is.
Only active schemes that a fund has enabled for you, on an active relationship, are returned. A scheme you were not given is treated like one that does not exist.

Endpoint: GET /schemes/nav
Version: 1.0.0
Security: JWT

## Security:

  - `JWT` (unknown)
    http bearer JWT

## Query parameters:

  - `scheme_code` (string, required)
    The scheme code the fund gave you. Matching ignores case and surrounding spaces.

  - `nav_date` (string)
    Return the NAV of this date (`YYYY-MM-DD`) instead of the latest.

  - `page` (integer)
    Page number, starting at 1.

  - `per_page` (integer)
    Results per page, up to 100.

## Response 200:

  - `200` (unknown)
    The scheme's NAV, in a list.

## Response 200 fields (application/json):

  - `data` (array)

  - `data.amc_name` (string)
    The fund house, as the registrar names it.
    Example: Example Asset Management (IFSC) Private Limited

  - `data.scheme_code` (string)
    Example: SCH001

  - `data.isin` (string)
    Example: INF000A01234

  - `data.scheme_name` (string)
    Example: Example Global Equity Fund Class A

  - `data.plan` (string)
    Enum: "direct", "regular"

  - `data.nav` (string)
    The NAV per unit as a decimal string with exactly 6 decimal places, so it is never rounded through a floating-point number. For example, a NAV of 60 is sent as `60.000000`.
    Example: 85.606500

  - `data.nav_date` (string)
    The date the NAV applies to (`YYYY-MM-DD`).
    Example: 2026-11-12

  - `data.currency` (string)
    The currency of the NAV.
    Example: USD

  - `page_meta` (object)

  - `page_meta.current` (integer)
    Example: 1

  - `page_meta.previous` (integer | null)
    Example: null

  - `page_meta.next` (integer | null)
    Example: null

  - `page_meta.per_page` (integer)
    Example: 20

  - `page_meta.pages` (integer)
    Example: 1

  - `page_meta.count` (integer)
    Example: 1

## Response 400:

  - `400` (unknown)
    Bad request — `scheme_code` is missing or blank, or `nav_date` is not `YYYY-MM-DD`. Validation errors carry a `Validation failed: ` prefix in `message`.

## Response 400 fields (application/json):

  - `error` (string)
    Example: Bad Request

  - `message` (string)
    Example: Validation failed: Scheme code can't be blank

## Response 401:

  - `401` (unknown)
    Unauthorized — missing or invalid JWT token.

## Response 401 fields (application/json):

  - `error` (string)
    Example: Unauthorized

  - `message` (string)
    Example: Missing token

## Response 403:

  - `403` (unknown)
    Forbidden — distributor access is not enabled for your business.

## Response 403 fields (application/json):

  - `error` (string)
    Example: Forbidden

  - `message` (string)
    Example: Distributor access not enabled

## Response 404:

  - `404` (unknown)
    Not found — the scheme code is not one you may sell, or it has no NAV for `nav_date`.

## Response 404 fields (application/json):

  - `error` (string)
    Example: Not Found

  - `message` (string)
    Example: No NAV found for this search

