This endpoint supports sequential batch order placement from a single endpoint. A maximum of 20 orders can be placed simultaneously.The difference between this interface and "Batch Add Orders" is that this interface will synchronously return the order information after the order matching is completed.For higher latency requirements, please select the "Batch Add Orders" interface. If there is a requirement for returning data integrity, please select this interface.
This endpoint only supports order placement requests. To obtain the results of the order placement, you will need to check the order status or subscribe to Websocket to obtain information about the order.
Please note that once your order enters the order book, the system will freeze the handling fees for the order ahead of time.Before placing orders, please be sure to fully understand the meaning of the parameters for each trading pair.
The maximum number of active orders per account is 2000, with a maximum of 200 active orders per trading pair.
| Param | Type | Mandatory | Description |
|---|
| clientOid | String | No | Client Order ID, unique identifier created by the user, the use of UUID is recommended |
| symbol | String | Yes | symbol |
| type | String | Yes | Order type ‘limit’ and ‘market’ |
| side | String | Yes | ‘buy’ or ‘sell’ |
| stp | String | No | self trade prevention is divided into four strategies: ‘CN’, ‘CO’, ‘CB’, and ‘DC’ |
| tags | String | No | Order tag, length cannot exceed ‘20’ characters (ASCII) |
| remark | String | No | Order placement remarks, length cannot exceed ‘20’ characters (ASCII) |
Additional Request Parameters Required by ‘limit’ Orders| Param | Type | Mandatory | Description |
|---|
| price | String | Yes | Specify price for currency |
| size | String | Yes | Specify quantity for currency |
| timeInForce | String | No | Order timing strategy ‘GTC’, ‘GTT’, ‘IOC’, ‘FOK’ (the default is ‘GTC’) |
| cancelAfter | long | No | Cancel after ‘n’ seconds, the order timing strategy is ‘GTT’ |
| postOnly | boolean | No | passive order labels, this is disabled when the order timing strategy is ‘IOC’ or ‘FOK’ |
| hidden | boolean | No | Hidden or not (not shown in order book) |
| iceberg | boolean | No | Whether or not only visible portions of orders are shown in iceberg orders |
| visibleSize | String | No | Maximum visible quantity in iceberg orders |
Additional request parameters required by ‘market’ orders| Param | Type | Mandatory | Description |
|---|
| size | String | No | (Select one out of two: ‘size’ or ‘funds’) |
| funds | String | No | (Select one out of two: ‘size’ or ‘funds’) |
For limit price purchase orders, we will hold the amount of funds (price * size) required for your purchase order. Similarly, for limit price sell orders, we will also hold you sell order assets. When the transaction is executed, the service fees will be calculated. If you cancel a portion of a filled or unfilled order, then the remaining funds or amounts will be released and returned to your account. For market price buy/sell orders that require specific funds, we will hold the required funds in from your account. If only the size is specified, we may freeze (usually for a very short amount of time) all of the funds in your account prior to the order being filled or canceled.When an order placement request is successful (the matching engine receives the order) or denied (due to there being insufficient funds or illegal parameter values, etc.), the system will respond to the HTTP request. When an order is successfully placed, the order ID is returned. The order will be matched, which could result in it being fully or partially filled. When an order is fully or partially filled, the remaining portions of the order will be in an active state awaiting to be matched (this does not include IOC orders). Orders that are fully or partially filled (already canceled) will be put into the “done” state.Users that have subscribed to the Market Data Channel can use the order ID (orderId) and client ID (clientOid) to identify messages.Price Protection MechanismsPrice protection mechanisms ae enabled for order placements. Rules are detailed below:If the spot trading market order/limit order placed by the user can be directly matched with an order in the current order book, the system will judge whether deviation between the price corresponding to the transaction depth and the spread exceeds the threshold value (the threshold value can be obtained using the symbol API endpoint);
If it is exceeded, for limit orders, the order will be directly canceled;
If it is a market order, then the system will partially execute the order. The execution limit will be the order size within the price range corresponding to the threshold value. The remaining orders will not be filled.
