improved

Addition of some fields on MyOrder Response and Change of Cancel Event Emission Logic & Addition of Identifier to Order-related Rest APIs (Scheduled for December 4th)

Dear Traders,

We want to inform you of the changes to the Open API and the schedule for these changes.

*Please be aware that these changes will affect the responses of MyOrder and Order-related Rest API, so it is crucial to be informed.

[1. Addition of Response Fields for MyOrder]

👍

We will support the information frequently requested by users.

[API Reference] > [WEBSOCKET] > [Request and Response] > [MyOrder]

  • You can receive real-time updates on the status of your orders through MyOrder.
  • The following fields will be added to the MyOrder response: Document
Field NameDescription
trade_feeFee incurred upon the trade
(null if not trade type)
is_makerIndicates whether the order is a maker or taker for which a match has occurred
(null if not trade type)
identifierUser custom value for the query
(Provided only for orders created after October 18, 2024)

[2. Change in the 'cancel' state emission logic for best/price order types in MyOrder]

👍

Improved to a more intuitive logic.

[API Reference] > [WEBSOCKET] > [Request and Response] > [MyOrder]

  • Before: For best and price (market order - bid) order types, no cancel event is emitted if there is even one trade. (including the case where the remaining amount is canceled because it is too small)
  • After: For best and price (market order - bid) order types, a cancel event will be emitted even in the above case.

[3. Addition of identifier Field to Order-related Rest APIs]

👍

We support the convenient use of identifier across all order-related APIs.


[Schedule]

  • Scheduled for implementation on Wednesday, 4th December, 2024.
  • These changes may impact the Open API service.

If you have any inquiries, please contact us at [email protected], and we will promptly address your concerns.

Thank you.