Registered Funds
Subscriptions, redemptions and transfers in registered funds, through the same transaction API as private companies.
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.
Registered funds run on the same unified transaction API as private company SPVs. If you have built the private companies flow, most of this will be familiar — the differences are in what a fund order carries and which sides it accepts.
Important: Registered fund subscriptions are created with
POST /primary/v2/transactionandtargetAssetType: "RegisteredFund". Earlier documentation described a/primary/v1/registered-fund-subscriptionfamily withpreview,sign-investorandsign-advisorendpoints and aTemplate/TemplateFilled/InvestorSigned/AdvisorSignedstatus lifecycle. None of that exists. There is no such path in the API, and the statuses it described were never the ones a partner sees. Build against the transaction API.
In This Section
- Registered Funds Overview: what a registered fund is here, and how it differs from an SPV
- Fund Discovery and Detail: listing funds and building a fund page
- Subscription Transaction: creating an order, and the fields registered funds add
- Action Workflow: what differs from the private companies action flow
What Differs From Private Companies
| Pre-IPO SPV | Registered fund | |
|---|---|---|
| Sides accepted | Subscription only | Subscription, Redemption, Transfer, Commitment, CapitalCall |
| Exit | No redemption | Redemption |
| Share class | Not applicable | shareClassId on the order |
| Distribution election | Not applicable | distributionElection on the order |
| Tax lot election | Not applicable | taxLotElection on a redemption |
| Statuses reachable | Six | All eight, including Initiated and PendingCancellation |
Updated about 17 hours ago