HTX is going to support “TRADE ID” in existing market data API feed
- API Announcements
Dear API user,
Since the effective day of this notification,
HTX will be including a new response field TRADE ID in following REST endpoints –
1) GET /market/trade query for latest market trade;
2) GET /market/history/trade query for recent market trades.
At the same time, HTX will be including TRADE ID in existing Websocket subscription/request too –
1) market.$symbol.trade.detail subscribe latest market trade;
2) market.$symbol.trade.detail request for latest market trade.
TRADE ID is unique identifier for each market trade. Even though a taker’s order matching with multiple maker’s orders simultaneously, each trade should be given individual TRADE ID.
This data enhancement is only applicable to above public API. For private API, e.g. history trades query endpoint “GET /v1/order/matchresults”, TRADE ID will not be added at this time.
Effective Date: October 9, 2019 (GMT+8)
All the changes will be updated on 【API Docs】
HTX
October 9, 2019
The following are change details:
1.REST API – query for latest market trade(s)
GET /market/trade (public endpoint)
GET /market/history/trade (public endpoint)
Request parameter(s)
Same as current.
Response:
Parameter | Data Type | Description | Value Range |
id | int | Unique trade ID | |
trade-id | int | Unique trade ID (NEW) | |
price | float | Trade price | |
amount | float | Trade volume | |
ts | int | Trade time (unix time in millisecond) | |
direction | string | Aggressive order side (buy or sell) |
2. Websocket API – subscribe/query for latest market trade(s)
market.$symbol.trade.detail (public endpoint)
Request parameter(s)
Same as current.
Response:
Parameter | Data Type | Description | Value Range |
id | int | Unique trade ID | |
trade-id | int | Unique trade ID (NEW) | |
price | float | Trade price | |
amount | float | Trade volume | |
ts | int | Trade time (unix time in millisecond) | |
direction | string | Aggressive order side (buy or sell) |