Published Pre-IPO integration
Discover published offerings and distinguish virtual Sandbox commitments from real reservations.
Explore endpoints
1 of 1/opportunities
Private credit & pre-IPO
Full endpoint documentationlistOpportunitiesReturns open private credit deals and pre-IPO opportunities available to your sub-accounts. Each deal has a minimum ticket size, close date, and target return.
Parameters
typeALL | PRE_IPO | OPPORTUNITYqueryExample: ALL
Headers
AuthorizationstringRequiredBearer sk_sandbox_<your_key> for sandbox requests.
Response fields
opportunitiesobject[]Requiredopportunities[].idstringRequiredopportunities[].assetTypePRE_IPO | OPPORTUNITYRequiredopportunities[].namestring | nullRequiredopportunities[].currencystringRequiredopportunities[].expectedReturnnumber | string | nullRequiredopportunities[].minInvestmentnumber | nullRequiredopportunities[].pricePerSharenumber | nullopportunities[].minimumSharesnumber | nullopportunities[].catalogueSourcePUBLISHED | SYNTHETICSandbox only. Published catalogue information or a synthetic demonstration product.
opportunities[].simulationOnlybooleanSandbox only. Does not create a real IPO reservation.
opportunities[].commitmentCurrencyUSDopportunities[].minimumCommitmentUsdnumber | nullopportunities[].subscriptionAvailablebooleanopportunities[].subscriptionRestrictionstring | nullopportunities[].targetAmountnumber | nullRequiredopportunities[].currentRaisednumber | nullRequiredopportunities[].riskLevelstring | nullRequiredopportunities[].statusstring | nullRequiredopportunities[].descriptionstring | nullRequiredopportunities[].maturityDatestring | nullRequiredopportunities[].expectedExitDatestring | nullRequiredopportunities[].createdAtstring | nullRequiredcountintegerRequiredResponse codes
200Open opportunities.What can a partner browse?
GET /opportunities?type=PRE_IPO includes published offering information with PUBLISHED, LISTED or ALLOCATED status, including Dangote when published. catalogueSource distinguishes PUBLISHED information from SYNTHETIC demos. Sandbox rows have simulationOnly: true. Neither publication nor Sandbox availability guarantees production allocation eligibility.
How do we commit virtual funds?
Follow the executable Pre-IPO recipe. Obtain an actual ID from the list, read /opportunities/{id}, check subscriptionAvailable, subscriptionRestriction and minimumCommitmentUsd, then submit { assetType: "PRE_IPO", assetId, amount } to the Sandbox customer's subscribe endpoint with a stable Idempotency-Key.
The customer must already have sufficient virtual USD. IDs are canonical subscription identifiers; slugs are browsing aliases. No real shares, production reservations, customer wallets or offering funding totals change. Verify the resulting virtual holding, order and wallet, then replay the identical request to prove it cannot debit twice.
What does admin handle?
/admin/partners tracks partner access and acceptance evidence. /admin/pre-ipo owns real published offering information and the actual offering lifecycle. Keep those controls distinct from virtual Sandbox commitments. Production eligibility, reservation and allocation require their separate reviewed workflow.
What errors should we handle?
An unknown or unpublished offering returns 404. Wrong asset type, unavailable USD terms or a below-minimum virtual commitment are rejected. Display the returned restriction; do not invent FX or assume that a listed offering remains open for new real subscriptions.
See API Reference, acceptance and errors.
Was this page useful?
Your signal helps us tighten partner onboarding docs.
Last updated on