Coming soon: order placement over WebSocket becomes available on September 2, 2026, on the global platform only. The EU platform is not yet supported.
Rate limits
Cancel order
Request parameters
Themarket parameter routes the call, so it stays required even when the order id alone would identify the order. When both identifiers are supplied, client_order_id takes precedence — the response still reports the engine id, which confirms which order was hit.
Canceling by client order id follows the same shape:
Response
Theresult object is the standard order object with status CANCELED — see the order object reference. The mtime field advances to the cancellation time while ctime stays at placement, so the pair tells how long the order lived.
Groups need a different call. Use
order_cancel_conditional for OCO and OTO groups — passing a group id here returns error 6. Plain stop orders and TPSL legs, on the other hand, belong to this method.