Overview and API Guide
Monark Markets, Inc API overview and guide.
Integrating through Apex AscendOS?Read Building on Apex AscendOS next. The product guidance in these guides applies to you, but the endpoints, fields and statuses are Monark's, and that page lists the AscendOS equivalents.
Introduction
Monark's API suite lets brokerage and wealth platforms offer their investors a curated marketplace of private market investments. The APIs cover the whole lifecycle — discovery, eligibility, order, signature and settlement — and are designed so that your platform keeps full control of the investor experience.
Monark sources the shares, forms and administers the vehicle that holds them in partnership with Sydecar, produces the offering and subscription documents, and maintains positions, statements and tax documents. Your platform owns everything the investor sees.
Two product areas share this foundation:
| Product | What it offers | Guides |
|---|---|---|
| Private companies | Late-stage private company exposure through single-asset SPVs | Private Markets: Onboarding |
| Registered funds | Subscriptions, redemptions and transfers in registered funds | Registered Funds |
Fundamental Objects
| Object | Description |
|---|---|
| Partner | Your platform. Partners are the direct users of the API and provide investors with access to the marketplace, either directly or through B2B relationships with financial institutions. |
| Financial Institution | The broker-dealer, RIA or FFI that holds the relationship with the investor. Every investor belongs to one. A partner with a direct investor relationship uses a default financial institution. |
| Person / Entity | The investing party. A person is an individual; an entity is a company, trust or similar, and needs at least one controlling individual before it can trade. |
| Account | What an investment is held in. An account names its owners — one or more parties — and a registration type. Accreditation is recorded here. |
| Investor | The investor record for a party. A party id and an investor id are the same identifier, which is why the v1 investor endpoints address parties created through the v2 endpoints. |
| Pre-IPO Company | The private company an investor is getting exposure to. Carries descriptions, leadership, funding history, news, research and pricing. Company information is provided in partnership with Sacra. Not investable on its own. |
| Pre-IPO Company Investment | The shares an SPV holds in a company, and the terms it acquired them on. Not an investor's holding. |
| Pre-IPO Company SPV | The vehicle an investor actually subscribes to. Currently one SPV per investment. |
| Prospective Offering | A potential SPV that does not exist yet. Terms are given as ranges, and investors may only register non-binding interest. |
| Indication of Interest | A non-binding expression of demand against a prospective offering. No signature, no cash check. Aggregated demand is what tells Monark whether to source a deal. |
| Transaction | An investor's order — a subscription to an SPV, or a subscription, redemption or transfer in a registered fund. The record that carries it to close. |
| Transaction Action | A disclosure, acknowledgement, signature or questionnaire that must be completed before a transaction can proceed. Completing the last one is what makes a subscription binding. |
| Questionnaire | A set of questions a partner presents to an investor, used for preferences and qualification. Some offerings require one before an order can proceed. |
| Position | An investor's settled holding, with its cost basis and current value. |
Note: Earlier versions of these docs described an Investor Subscription and an Investor Subscription Action. Those are the v1 names for what are now the Transaction and Transaction Action. They are the same underlying records, and the v1 endpoints remain live, but v2 is the model to build against. One place still uses the older vocabulary: the
SubscriptionStatuswebhook. See Subscription Statuses (v1).
Where to Start
- Authentication & Environments — keys, base URLs, pagination, errors and the conventions every call follows.
- Private Markets: Onboarding — how the private companies product works, what Monark sets up, what you build, and in what order.
- Sandbox Walkthrough — one investor from account creation to a binding subscription, as a sequence of real calls.
Technical Notes
Data Access Patterns
Data Access Patterns covers how partners, investors and Monark each interact with the system's data, and how partner scoping is enforced.
Relationships and Dependencies
Relationships and Dependencies sets out how partners, financial institutions, investors, companies, SPVs and transactions relate, and which dependencies must be satisfied before an order is possible.
Status Transitions
Status Transitions documents the lifecycle of transactions, SPVs and investors. Read it before writing any code that branches on a status string — the values are case-sensitive, and the webhooks use a second vocabulary.
Webhooks
See Webhooks for registration, delivery and signature verification, and Webhooks for what each private markets event means for your platform.
Disclosure and Disclaimer
The information contained herein is provided for general informational purposes only and does not constitute legal or financial advice. No one should act, or refrain from acting, based solely on the content of this information without first seeking appropriate professional counsel specific to their individual needs. Use of or reliance on any information provided is solely at your own risk. Neither the provider nor any affiliated parties assume liability for actions taken based on the information contained herein. Always consult with qualified professionals regarding any legal or financial matter.
Updated 11 days ago