HTX is going to include a new field ‘fee-currency’ in existing match result endpoints

Dear API user,

Since the effective date of this notification, HTX will add one more field in the response message of following exising REST API endpoints –

GET /v1/order/orders/{order-id}/matchresults
GET /v1/order/matchresults

The request parameters and the other response fields remain same as existing.

Effective Date: June 24, 2020 (GMT+8)

All the changes will be updated on HTX API Docs.

HTX
June 23, 2020

 

Change Details

Since the effective date of this notification, HTX will add one more field in the response message of following exising REST API endpoints –

GET /v1/order/orders/{order-id}/matchresults
GET /v1/order/matchresults

fee-currency string Currency of transaction fee or transaction fee rebate (transaction fee of buy order is based on base currency, transaction fee of sell order is based on quote currency; transaction fee rebate of buy order is based on quote currency, transaction fee rebate of sell order is based on base currency)

It responses together with another field ‘filled-fees’, to indicator the corresponding currency ‘filled-fees’ based on. If ‘filled-fees’ shows a positive value, it implicates that a transaction fee being charged for the trade. In such a case, ‘fee-currency’ refers to the currency of the transaction fee. If ‘filled-fees’ shows a negative value, it implicates that a transaction fee rebate will be paid. In this case, ‘fee-currency’ refers to the currency of the rebate.

What are the Impacts on You, and What You Need to Do?

API users should evaluate the business impact caused by the enhancement, further to make relevant change in client’s application, if needed.

All the changes will be updated on HTX API Docs on the effective date.