Portfolio View

📘

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.

Once an investor has subscribed, your platform owns the ongoing view: where the order has got to, what the position is worth, and what arrives at tax time.

Monark endpoints used

Open orders

An investor who abandoned a flow part-way has a transaction sitting in Pending with actions outstanding. Surface it, with a way back in — otherwise the subscription is simply lost.

GET /primary/v2/transaction/investor/{investorId}?pageSize=50

Filter out the terminal statuses — Complete, Canceled, Failed — and show the rest with a route back to Transaction Actions.

Monark helps here: PendingSubscriptionReminder fires for a transaction left pending with actions outstanding. It is the event behind an abandoned-order nudge.

Positions and value

GET /primary/v2/transaction/{id} enriches a Complete transaction with its current value, derived from Monark's NAV marks for the SPV.

Note: The enrichment is best-effort. Current value and corporate actions are each fetched behind their own error handling, so a transaction can come back without them rather than failing outright. Render the absence rather than assuming the fields are present.

NAV marks are based on secondary market trading levels, available in real time and updated daily. They are marks, not executable prices — an investor cannot sell at the mark on demand, because secondary liquidity is event-driven. Say so where you display it.

Statements and tax

Monark provides:

• Monthly statements showing current value, gain and loss, and cost basis.
• K-1s, annually. Each SPV is a Delaware series LLC taxed as a limited partnership, so investors receive a K-1 rather than a 1099.

Both are served through the document endpoints. A K-1 arriving in a brokerage app that otherwise issues 1099s is worth explaining in your UI — it is the most common support question these investments generate.

Documents after close

After the SPV closes, the investor's documents are replaced with countersigned versions. An investor who downloaded a subscription agreement while their transaction was Processing has the signed-but-not-countersigned copy; re-fetch after Complete.

Corporate actions

Monark surfaces current and upcoming corporate actions affecting active SPVs, and raises a CorporateAction webhook. Use them to drive notifications or banners.

Where an event settles cash or shares — an acquisition, or an IPO — the settlement happens directly with your custodian, not through Monark's API. Your operations team needs to know this; your investor needs to be told what is happening to their position.

IPO lock-ups

Shares acquired privately are subject to a 180-day lock-up following an IPO, and remain restricted until it ends. An investor watching a company go public will expect to be able to sell, and will not be able to. Surface the lock-up and its end date rather than letting them find out by trying.

Selling

There is no redemption path for an SPV. A Pre-IPO SPV transaction can only ever be a Subscription, so an investor cannot sell a position back on demand.

Set this expectation early. An investor who assumed they could sell whenever they liked is the most common source of complaint in private markets.

Implementation notes

• Drive status from webhooks. SubscriptionStatus fires at every transition. Reconcile with the transaction endpoints rather than polling them.
• Watch the status vocabulary. The webhook carries the v1 enum, where a v2 Canceled arrives as Rejected. See Webhooks.
• Release reserved cash when a transaction reaches Canceled or Failed. Monark never held it, so nothing else will.
• Reconcile on referenceId. GET /primary/v2/transaction filters on it, which is the simplest bridge between Monark's records and your own ledger.

Next steps

• The statuses driving this page: Transactions