Submit order
Place a single buy or sell order for a portfolio and receive the resulting asset transaction.
Authorizations
Auth0-issued access token that includes the scopes listed for the endpoint.
Headers
User identifier for the M2M client to specify which user's data to access.
^[a-f0-9]{24}$Body
- Option 1
- Option 2
- Option 3
- Option 4
Asset order request. Exactly one branch applies:
- Market buy —
side: buy,amountrequired;orderTypeomitted orMarket; optionalexecuteEtfOrdersInRealtime.limitPriceandtimeInForceare not allowed. - Market sell —
side: sell,quantityrequired; same market rules as buy. - Limit buy —
side: buy,orderType: Limit,amount,limitPrice, andtimeInForcerequired.executeEtfOrdersInRealtimeis not allowed. - Limit sell —
side: sell,orderType: Limit,quantity,limitPrice, andtimeInForcerequired.executeEtfOrdersInRealtimeis not allowed.
buy ISIN of the asset to trade.
^[A-Z]{2}[A-Z0-9]{9}[0-9]$Whole-currency amount to invest.
x >= 0.01Order type. Omit to default to market.
Market Optional. Ignored for buy orders; included for backward compatibility.
x >= 0.0001Optional override for ETF instruments. Only users flagged for real-time execution can set this to true.
Response
Order created successfully.
Asset transaction enriched with display-ready fields.
AssetTransaction Current transaction status (Pending, PendingGift, Settled, etc.).
update, buy, sell User identifier owning the transaction.
Portfolio identifier associated with the transaction.
Execution windows separated by asset category (matches domain ExecutionWindowsType)
Wealthyhood fees on orders and settled transactions (commission, FX, and real-time execution when applicable).
Present for partner users when countervalue fees apply.