Order creation
The following operations not only require user authorization but often also require a wallet signature:
Withdrawal from trading account
Creation of limit, market, and stop-limit orders
Replacement of limit and stop-limit orders
Cancellation of limit and stop-limit orders
Position closure
Leverage change for positions
Creation, modification, and cancellation of TpSl
Withdrawal
This operation is executed via the POST /api/transfer/pf/withdraw REST API method by specifying the currency, withdrawal amount, recipient wallet address, and a signature.
Important: Before signing, all float values must be normalized to integers according to the documentation.
Important: The withdrawal request is pre-validated by the exchange. If funds are available, the user's trading account is locked until the operation completes.
Only unreserved funds (not tied to positions or orders) are eligible for withdrawal.
Order Creation
These operations use the following REST API methods:
POST /api/order/limit – create limit order
POST /api/order/stop-limit – create stop-limit order
POST /api/order/market – create market order
All the methods require a signature. Signature schemas
Important: Normalize all float values to integers before signing according to the documentation.
Important: Orders are pre-validated by the exchange. They may be rejected if the user lacks sufficient free margin or if limits are violated.
Important: Orders are processed asynchronously. A NEW status in the response only guarantees entry into the Order book but not execution.
Order Replacement
These operations use the following REST API methods:
PUT /api/order/{orderId}/limit – replace limit order
PUT /api/order/{orderId}/stop-limit – replace stop-limit order
PUT /api/order/limit/{instrument} – batch replace orders
All methods require a signature. Signature schemas
Important: Normalize all float values to integers before signing according to the documentation.
Order Cancellation
These operations use the following REST API methods:
DELETE /api/order/{orderId} – cancel specific order
POST /api/order/mass-cancel – cancel all user orders for an instrument
POST /api/order/mass-cancel-by-id – cancel specific user orders
These methods do not require a signature.
Important: If the order is filled before the cancel request is processed, its status will not be changed to CANCELLED.
Position Closure
This operation uses the POST /api/position/{instrument}/close REST API method, specifying the position volume to be closed.
Important: Normalize all float values to integers before signing according to the documentation.
Leverage Change
This operation uses the PUT /api/position/{instrument} REST API method, specifying the new leverage.
No signature is required.
TpSl Creation, Modification, and Cancellation
These operations use the following REST API methods:
POST /api/tpsl/{instrument} – create TpSl
POST /api/tpsl/{instrument}/id – modify TpSl
DELETE /api/tpsl/{instrument}/id – cancel TpSl
Signature is required for creation. Signature schema
Important: Normalize all float values to integers before signing according to the documentation.
Important: All active TpSl orders will be canceled during liquidation.
Last updated