Dear API user,
Since the effective day of this notification, Huobi Global will be supporting a new endpoint “GET /v1/account/history” in REST API for account history querying (API Key Permission: Read).
Effective Date: October 22, 2019 (GMT+8)
All the changes will be updated on 【API Docs】
Huobi Global
October 21, 2019
The following are change details:
Request Parameters
Field Name | Mandatory | Data Type | Description |
account-id | true | string | Account ID |
currency | false | string | Currency Default value: all |
transact-types | false | string | Amount change types (multiple selection allowed) Default value: all Enum values: trade etf transact-fee deduction transfer credit liquidation interest deposit-withdraw withdraw-fee exchange other-types |
start-time | false | long | Far point of time of the query window (unix time in millisecond) Searching based on transact-time Value range: [((end-time) – 1hour), (end-time)] The maximum size of the query window is 1 hour Default value: ((end-time) – 1hour) The query window can be shifted within 30 days |
end-time | false | long | Near point of time of the query window (unix time in millisecond) Searching based on transact-time Value range: [(current-time) – 29days,(current-time)] The maximum size of the query window is 1 hour Default value: current-time The query window can be shifted within 30 days |
sort | false | string | Sorting order Enum: asc desc default value: asc |
size | false | int | Maximum number of items in each response Value range: [1,500] Default value: 100 |
Response
Field Name | Data Type | Mandatory | Description |
status | string | true | Status code(ok or error) |
data | object | true | |
{ account-id | long | true | Account ID |
currency | string | true | Currency |
transact-amt | string | true | Amount change(positive value if income, negative value if outcome) |
transact-type | string | true | Amount change types |
avail-balance | string | true | Available balance |
acct-balance | string | true | Account balance |
transact-time | long | true | Transaction time (database time) |
record-id } | string | true | Unique record ID in the database |
Comments
0 comments
Article is closed for comments.