POST /orders-v3. The field-by-field reference lives on the
endpoint page.
Prerequisites
You also need your API key, sent asx-sx-api-key. See
Authentication and API key.
Steps
GET /metadata/obv3— chain id, Escrow address, active token, ladder step, size limits.- Round your odds down onto the ladder — a multiple of
oddsLadderStepSize × 10^15. See Odds rounding. - Choose a
timeInForce—GTCto rest,IOC/FOKto execute now. See Time in force. - Sign the eight-field EIP-712
Orderstruct. POST /orders-v3— expect200and a per-order result carryingSUBMITTED, the server-assignedcommandId, and yourclientOrderId/externalUserIdif you set them.- Watch your
account:orders_v3stream for the transition instead of polling. Or setwaitForOutcome: trueto have the call wait and return each order’s terminaloutcomeinline.
Posting an order does not lock capital, regardless of
timeInForce. Funds are only escrowed when
the order matches — see Risk limits.Posting a GTC order end to end
expiry is required and must be a unix epoch timestamp in seconds (not milliseconds) that is in
the future. An expiry that falls inside the market’s betting delay plus two seconds is rejected.Post-only
postOnly: true on a GTC order makes it add liquidity only — if it would cross the book on arrival
it is cancelled with inactiveReason: "POST_ONLY_WOULD_CROSS" instead of matching. See
Time in force.
JavaScript
Batching
POST /orders-v3 takes an array of up to limits.maxCreateOrders orders (currently 10), one
shared maker per batch — the full field rules are on Create orders.
- One maker per request. Every order in the batch must carry the same
maker. Mixed makers are a400. - Batches are not atomic. A partial outcome is normal. Always read the status of every entry in the array.
Dust remainders
A partial fill that would leave a remainder below
limits.minRestingOrderSizeBaseUnits does not rest that remainder.
The order then goes terminal: status: "INACTIVE" with inactiveReason: "FILLED".Re-quoting
There is no amend. To move a price: cancel, then post a new order.Related
Create orders
Every field, every validation rule.
Taking liquidity
The same signing and submission path, from the taker’s side.
Time in force
Choosing between GTC, IOC and FOK.
Tracking your orders
Reading your own orders back, and what the API will not tell you.
Market making
Quoting, exposure and re-quote loops.
External user id
Tag orders when one SX account places bets for many people.