Endpoint
Description
Supports both single modify ("modify") and batch modify ("batchModify").
Use the exchange signing flow
with the account owner or an approved API wallet. Hyperliquid and Polymarket outcome orders cannot
be modified; cancel and replace them instead. Spot modifications are available only when enabled
by the deployment and only for eligible resting limit orders.
Request Body
action
For
modify, both oid and order are required. For batchModify, modifies must contain at
least one item. Use the string Notional order ID returned by the API, not a numeric venue order ID.
action.modifies[]
action.order and action.modifies[].order
The market and side remain those of the stored order.
s is the new total size, including any
already filled quantity. A limit order’s t.limit.tif must remain unchanged (Gtc, Ioc, or
Alo). A trigger’s tpsl and isMarket fields are also immutable. Local stop-market TP/SL can be
modified before it fires; venue-backed trigger orders require cancel and replacement.
A resting reduce-only order may be modified. Its new size is admitted against the market’s free
close capacity: a size that would push your live closing orders past the position is rejected with
code: "CLOSE_CAPACITY_EXCEEDED" and free: "<size>" (the remaining close capacity as a decimal
string), and a modify of a closing order while an immediate close is superseding the market’s
resting closes is rejected with code: "CLOSE_IN_PROGRESS".
financing is unsupported and explicitly rejected in the replacement order specification.
Response
The server echoes the incoming action type:- 200: Confirmed
- 200: Pending
- 200: Rejected
