Cancel an existing order and create a new one with the same market and order side (bid/ask) in a single request.
Request Parameter
| Field | Description | Type |
|---|---|---|
| prev_order_uuid | UUID of order to cancel | String |
| prev_order_identifier | User custom value for order to cancel | String |
| new_ord_type * | New order method - limit : Limit Order- price : Market Price Order(Bid)- market : Market Price Order(Ask)- best : Best Order type(time_in_force field is required) | String |
| new_volume * | New Order Volume (Required for ask limit and ask market order type) - To use the remaining order from previous existing order, set remain_only for the new order.- remain_only is supported only for limit, limit IOC/FOK, market ask, and best ask orders. | NumberString or remain_only |
| new_price * | Order Price (Required for ask limit and ask market order type) ex) In the KRW-BTC market, if you're trading at 1,000 KRW per 1 BTC, the price value should be set to 1000. ex) In the KRW-BTC market, if the best ask price is 500 KRW per 1 BTC, setting the price value to 1000 when placing a market bid order will purchase approximately 2 BTC. (Note: The actual amount of BTC purchased may vary depending on trading fees and the available quantity at the best ask price.) | NumberString |
| new_identifier | User custom value for new order (Optional) | String (Unique Value) |
| new_time_in_force | ioc, fok order settings for new order* (*This field only works when the ord_type is limit or best.)- ioc : Immediate or Cancel- fok : Fill or Kill | String |
* Required
* Required under specific conditions
This API only supports the application/json Content-Type format. Please note that requesting with other formats such as query parameters or form-data are not supported.
Either
prev_order_uuidorprev_order_identifiermust be included.
new_identifierandprev_order_identifiermust be different.The identifier is a key value that is issued directly by the user, not by the service. It is used to uniquely identify orders and must be unique for each order.
When canceling and placing a new order, a new identifier is required.
If an error occurs during the request, please do not resend the request with the same identifier and generate a new identifier for each request.
Response
| Field | Description | Type |
|---|---|---|
| uuid | Unique Order ID for the order to be canceled | String |
| side | Order Type for the order to be canceled | String |
| ord_type | Order Method for the order to be canceled | String |
| price | Price of the order to be canceled | NumberString |
| state | Order Status for the order to be canceled | String |
| market | Market Unique Key for the order to be canceled | String |
| created_at | Order Generation Time for the order to be canceled | String |
| volume | User Input Order Volume for the order to be canceled | NumberString |
| remaining_volume | Remaining Order Volume after Trade for the order to be canceled | NumberString |
| reserved_fee | Ratio Reserved as Fees for the order to be canceled | NumberString |
| remaining_fee | Remaining Fees for the order to be canceled | NumberString |
| paid_fee | Used Fees for the order to be canceled | NumberString |
| locked | Ratio being used in Transactions for the order to be canceled | NumberString |
| executed_volume | Traded Volume for the order to be canceled | NumberString |
| trades_count | The number of Transactions in the order for the order to be canceled | Integer |
| time_in_force | ioc, fok order settings for the order to be canceled | String |
| identifier | User-defined identifier for retrieving the order to be canceled *The identifier field is provided only for orders placed on or after October 18, 2024. | String |
| new_order_uuid | Expected UUID of the new order (if succeed) | String |
| new_order_identifier | User customized order ID of the the new order (if succeed) | String |
New Order
The new order will be placed in the same market as the existing order after the existing order (corresponding to
prev_order_uuidorprev_order_identifier) has been completely canceled.If the new order has been successfully placed, you can query it by
new_order_uuidprovided in the response ornew_identifierspecified by the user upon request.Even if the cancel and new request is successfully submitted, a new order won’t be created if the previous existing order has been fully filled before the cancelation.