outputMint to buy or inputMint to sell. A buy settles in one transaction (executionMode = sync) or in two (executionMode = async), and a sell always settles in one.
Equity Request Parameters
Sync or Async Execution
The market maker with the best price decides how a buy settles:sync if it has inventory, otherwise async. executionMode says which. A sell is always sync.
Equity Response Fields
The response is anOrderResponse. A response settled by a market maker adds these fields:
submitEndpointRequired is present, and true, only when the response goes to the submit transaction endpoint. A sync response that includes the market maker’s fill instruction always sets it.
The scaled fields are present only when the equity mint carries the Token-2022 Scaled UI Amount extension, which stores a multiplier on the mint while token accounts hold the raw amount. The multiplier accounts for stock splits and dividends, so a scaled amount can be compared against the raw underlying price. A sell adds inAmountScaledUi, and a buy adds outAmountScaledUi and minOutAmountScaledUi. Each scales the matching amount and truncates it:
outAmountScaledUi = floor(outAmount × scaledUiMultiplier) / 10^decimals
For a mint with 9 decimals and a scaledUiMultiplier of 1.2:
outAmountis"2500000000".outAmountScaledUiis"3"(2500000000 × 1.2 / 10^9), so you show 3, not 2.5.
Submit Equity Transactions
The submission path depends on theexecutionMode and submitEndpointRequired in the order response.
Submit an Async Response
The transaction of anasync response is complete once the user signs it. Send it to Solana through your own RPC, then track it as in Track an Async Equity Order.
Submit a Sync Response
A response withsubmitEndpointRequired: true goes to the submit transaction endpoint. Any other response goes through your own RPC. The endpoint accepts v0 and v1 transactions.
How the Submit Transaction Endpoint Differs from a Solana RPC
- The submit transaction endpoint accepts only the transaction
/orderreturned, plus the user’s signature (and the sponsor’s, when the request sets one). It rejects a transaction whose terms were changed. - The submit transaction endpoint serves
sendTransactiononly, and ignores configuration fields other thanencoding.