Data Access Patterns
Which parties can see and change what, and how Monark enforces the boundary between partners.
Integrating through Apex AscendOS?These rules describe how Monark scopes data between the partners that call it directly. When you build on AscendOS, Apex is that partner. See Building on Apex AscendOS.
Access is scoped so that partners share a marketplace without sharing their investors. This page sets out who can see what, and how the boundary is enforced.
How scoping works
A partner API key carries a partner id, and every query is filtered by it before it reaches the database. This is structural, not a convention layered on top.
Note: A consequence worth knowing when you are debugging: another partner's record reads as a
404, not a403. "Not found" frequently means "not yours". Before assuming an id is wrong, check whose it is.
Within a partner, data is further scoped by financial institution. Offerings, prospective offerings and market data are all requested against a financialInstitutionId, and an investor belongs to exactly one.
Partner access
- Partners can access, view and update only their own investors. Another partner's investors are invisible.
- Partners can access all Pre-IPO companies, company investments and SPVs. The catalogue is shared.
- Partners can view the indications of interest and questionnaire responses submitted by their own investors.
- Partners can create investors, accounts, indications of interest, transactions and questionnaire answers.
- Partners approve SPVs for distribution to their own investors, in the Alts Desk or through the partner approval endpoints. An approval by one partner does not make an SPV investable for another.
Investor access
- Investors can view attributes, research, news and other content for all Pre-IPO companies, company investments and SPVs. Your platform builds the experience they see.
- Investors can submit transactions, indications of interest and questionnaire responses, and can view their own holdings.
- Investors can view templated versions of subscription agreements, PPMs and other offering documents relevant to an SPV. After a successful subscription they can view the signed versions, and after the SPV closes the countersigned versions.
- After close, investors can view their tax documents. Monark provides K-1s annually through the API.
Monark access
- Monark can aggregate and view indication of interest and questionnaire data across all partners. This is what informs sourcing decisions on prospective offerings.
- Monark creates Pre-IPO companies, SPVs, company investments and questionnaires.
- Monark maintains the audit trail for all transactions and events.
Fields you will not receive
Some fields are marked admin-only and are removed from partner responses — absent from the JSON, not returned as null.
The ones most likely to matter:
| Object | Fields absent from partner responses |
|---|---|
| Transaction | managementFee, feePerShare, carry |
| SPV | assetType, securityType, round, valuationType, monarkStageHistory, totalManagementFee, monarkSplit, demandSplit, createdAt, isTestData |
Important: Fee economics for an order are not on the transaction. Read them from the SPV —
managementFee,investorFeePerShareandallInPricePerShareare all present there. A mapper written against a full field list will silently produce nulls.
Next steps
- The conventions every request follows: Authentication & Environments
- How the entities relate: Relationships and Dependencies
Updated 12 days ago