Subscription Statuses (v1)
The legacy v1 subscription vocabulary, where your platform still meets it, and how it maps to the transaction statuses.
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's private markets API has two generations. The current one models an order as a transaction; the earlier one modelled it as an investor subscription. They are the same underlying record, and Transactions is the model to build against.
This page exists because one place still speaks the older vocabulary, and it is a place you cannot avoid.
Where you still meet it
Important: The
SubscriptionStatuswebhook reports v1 statuses, not v2 transaction statuses. If you drive order state from webhooks — which you should — you will receive this vocabulary.
The v1 endpoints under /primary/v1/investor-subscription also remain, operating on the same rows. Use /primary/v2/transaction for new work.
The v1 statuses
| Status | Meaning |
|---|---|
Pending | Actions outstanding |
Processing | Signed and binding |
Settled | Cash settled with an external account |
Complete | Closed and countersigned |
Rejected | Cancelled |
Failed | Failed |
The mapping
v2 TransactionStatus | v1, as the webhook sends it |
|---|---|
Pending | Pending |
Processing | Processing |
Settled | Settled |
Complete | Complete |
Canceled | Rejected |
Failed | Failed |
Initiated | no equivalent |
PendingCancellation | no equivalent |
The rename is the one that costs people time: a cancellation your API read calls Canceled arrives by webhook as Rejected. A platform matching on Canceled in its webhook handler will silently never fire.
Initiated and PendingCancellation have no v1 representation at all. Neither is reachable for a Pre-IPO SPV subscription, so this matters only for registered-fund and drawdown transactions.
What to do about it
Normalise at the boundary. Map the incoming webhook status to your own internal vocabulary in one place, rather than spreading two spellings of "cancelled" through your codebase.
Next steps
- The current model: Transactions
- Handling the events: Webhooks
Updated about 17 hours ago