Fund Discovery and Detail

📘
Integrating through Apex AscendOS?
The product guidance on this page applies to you. The endpoints, fields and statuses are Monark's; use the AscendOS equivalents listed in Building on Apex AscendOS.

Monark endpoints used

Method	Endpoint	Purpose
`GET`	`/primary/v1/registered-fund`	List funds
`GET`	`/primary/v1/registered-fund/{id}`	One fund, in full

List funds

GET /primary/v1/registered-fund?page=1&pageSize=25

Returns the standard { items, pagination } envelope. See Authentication & Environments for the pagination conventions.

Fund and share class data changes infrequently, so caching the list for the length of a session keeps a marketplace responsive.

The fund page

A fund page answers the questions an investor asks before committing: what the fund invests in, who runs it, what it costs to get in, and how liquid it is.

UI element	Monark field	Notes
Name and logo	The fund's name and logo fields
Manager	The fund manager
Strategy or asset class	The fund's classification
Share classes	The fund's share classes	An order names one. Minimums usually differ between them
Minimum investment	The lowest initial minimum across share classes	Show a single entry minimum on a card; break it out per class on the detail page
Documents	The fund's document set	Prospectus and related offering material

Note: Which fields a given fund publishes varies. Null-guard each one and design for the sparse case rather than assuming a complete record.

Eligibility

Registered funds carry their own investor eligibility requirements, and some are restricted to accredited investors, qualified clients or qualified purchasers. Record the relevant status on the account before presenting a restricted fund — see Accreditation.

Where your platform knows the active account, flag funds whose requirements the account does not meet rather than letting an investor reach an order form they cannot submit.

Next steps

Create the order: Subscription Transaction