Fund Detail

The fund detail page is where a user decides whether to invest. Evergreen funds are offered continuously, so this page is both the diligence view and the starting point for every subscription into the fund. It needs to make three things clear before the user reaches an order ticket: what the fund is, how and when money can move in and out of it, and what it costs.

Endpoints used

Workflow

1. Retrieve the fund by id with includeDocuments=true. The response includes its share classes (each with NAV reports and fees), fund-level fees, and documents.
2. Retrieve NAV history for the selected share class.
3. If the fund has a cik and your platform licenses EvergreenLink, load the EvergreenLink sections.
4. Show an "Invest" action that carries the fund's id, and the selected share class, into the order flow.

Fund profile

GET /primary/v1/omnibus/fund/{id}?includeDocuments=true

The reference implementation's header also shows net assets, a trailing return, and a distribution yield. Those figures come from EvergreenLink, the optional data set described below, and not from the fund endpoint.

Terms and liquidity

Evergreen funds accept subscriptions and redemptions on a schedule, and most limit how much of the fund can be redeemed in each window. Users need to understand this before they invest, so give the fund's liquidity terms a prominent place on the page rather than leaving them to the prospectus.

Note: The process fields are written by the fund and can run to several sentences. Display them in full. Do not attempt to parse dates or percentages out of them.

Share classes

Orders are placed against a share class, never against the fund. List the fund's share classes from Fund.shareClasses and have the user choose one before they invest. To load them on their own, use:

GET /primary/v1/omnibus/share-class?omnibusFundId={fundId}

Offering the right share class for the account type - advisory, brokerage, or retirement - is your platform's responsibility. If your firm distributes only some of a fund's share classes, filter the list before you show it.

NAV history

Evergreen funds transact at net asset value, which is reported per share class.

GET /primary/v1/omnibus/nav-report?omnibusShareClassId={shareClassId}&startDate=2025-01-01

{
  "items": [
    {
      "id": "01a0617a-0000-7000-8000-0000000000a1",
      "omnibusShareClassId": "01a06194-0000-7000-8000-0000000000c1",
      "reportDate": "2026-08-31",
      "nav": 25.41
    }
  ],
  "pagination": { "totalRecords": 20, "totalPages": 1, "currentPage": 1 }
}

Important: The latest NAV is the last price the fund reported, not necessarily the price an order will receive. Orders fill at the next NAV the fund strikes, except that a netted fill on a monthly-NAV fund is priced at the last NAV the fund has published when the netting session runs. Label any figure that you derive from the latest NAV as an estimate.

Fees

Each fee belongs either to the whole fund or to a single share class. The fund response carries fund-level fees in Fund.feeStructures and each class's fees in Fund.shareClasses[].feeStructures. To load them on their own, query fund-level fees with omnibusFundId and class fees with omnibusShareClassId:

GET /primary/v1/omnibus/fee-structure?omnibusShareClassId={shareClassId}

When the user changes share class, update the fee table to show fund-level fees together with the fees of the selected class.

Documents

A fund's documents, such as its prospectus and fact card, are returned in Fund.documents when you request the fund with includeDocuments=true. To list them on their own, use:

GET /primary/v2/document?omnibusFundId={fundId}

If the fund has no documents, hide the section.

Note: Documents that a user must acknowledge or sign before investing are delivered through Pre-Order Requirements, not through this section. Listing a prospectus here does not record that the user has received it.

EvergreenLink fund data

The Omnibus endpoints describe what a fund is and how to trade it. EvergreenLink is a separate data set that answers a different question: how the fund has performed and what it holds. It is third-party data — drawn from each fund's own filings and reporting rather than from Monark's order book — which Monark ingests, normalises, and serves from the secondarylink/evergreen-* routes of the same API. If your platform licenses it, it is what turns a fund page into a research page.

The two data sets are joined on the fund's SEC Central Index Key, Fund.cik.

EvergreenLink access is granted per financial institution. Pass the financialInstitutionId of a custodian that Monark has enabled for it; other IDs return 403.

Call the growth endpoint first, filtered by cik. Every row it returns carries the evergreenFundId that the returns and share classes endpoints filter on — those two ignore cik.

If a fund has no cik, or its cik matches no EvergreenLink fund, hide these sections. An empty chart reads as missing data.

Invest action

Give the page a persistent primary action that starts the order flow for the active account. Platforms that support model portfolios can offer a second action that starts a Model Order for the same fund.

Disable the action, with an explanation, when no account is selected or when the account does not meet the fund's eligibility requirements.

Next steps

• Find out what the account must complete before it can invest: Pre-Order Requirements