Account & Trades (v2)
REST v2 under /api/v2/account for spot-relevant account flows (shared with contract accounts where the same key applies). U-margined futures v2: Account & Trades (v2).
Get account balance flow (USER_DATA)
GET /api/v2/account/balance-flow
Weight:5
Parameters
| Name | Type | Mandatory | Description |
|---|---|---|---|
| accountType | STRING | NO | MAIN or FUTURES (default MAIN) |
| coin | STRING | NO | token id |
| flowType | STRING | NO | flow type enum name (e.g. USER_ACCOUNT_TRANSFER); same naming as in data[].flowType |
| fromId | LONG | NO | from id |
| endId | LONG | NO | end id |
| startTime | LONG | NO | start (ms) |
| endTime | LONG | NO | end (ms) |
| limit | INT | NO | default 20, min 1, max 1000 |
| timestamp | LONG | YES | — |
| recvWindow | LONG | NO | — |
Response
json
{
"code": 200,
"msg": "success",
"data": [
{
"id": "539870570957903104",
"accountType": "MAIN",
"coin": "BTC",
"symbol": "BTCUSDT",
"flowType": "USER_ACCOUNT_TRANSFER",
"flowName": "Transfer",
"change": "-12.5",
"total": "379.624059937852365",
"created": "1579093587214"
}
]
}In the response,
idandcreatedare returned as string-typed numbers in JSON, consistent with other v2 list APIs. The legacy v1 flow listGET /api/v1/account/balanceFlowremains available; the v2 route uses string accountType and flowType and omits deprecated numeric-only fields in the public reference. See SIGNED for request signing.