Coming soon: order placement over WebSocket becomes available on September 2, 2026, on the global platform only. The EU platform is not yet supported.
order_limit_place accepts the full execution-flag set, including Retail Price Improvement. The response returns the accepted order in its initial state — OPEN for an order that rests, FILLED or PARTIALLY_FILLED when the order matches on arrival.
Rate limits
Place limit order
Request parameters
Theparams array carries exactly one element: an object holding the order parameters. Unlike the subscription channels, positional parameters are not used.
Prices and amounts are decimal strings, not numbers. Precision above the market setting is rejected with error 1; consult stepSize and tickSize via GET /api/v4/public/markets.
Response
Theresult object is the standard order object — see the order object reference. A limit order reports type 1.
Two response conventions apply. The side field inverts against the request: the request sends "buy" or "sell" as a string, while the response reports 1 for sell and 2 for buy. Trailing zeros are normalized on the way out, so a price sent as "1916.40" returns as "1916.4" — compare decimal values numerically, never by string equality.
Subscribe to Orders Pending to follow the order after placement, and to Deals for its individual fills.
Execution flags
Among the spot placement methods, onlyorder_limit_place accepts rpi. The flags constrain each other: ioc combines with neither post_only nor rpi, and rpi implies post_only. An illegal pair is rejected with error 1 rather than silently dropped — the full matrix is in Order Management.
While a market runs in post-only mode, only limit orders carrying the post-only flag are accepted; a market or stop method on the same market is rejected with error 51.
Error codes
Standard transport errors and the shared account, rate-limit, and region codes are listed in Order Management.Used in these guides
- Market Maker integration — placing and canceling quotes over the WebSocket order methods.