Trade

Account Trade List (USER_DATA)

Get trades for a specific account and symbol.

If fromId is set, it will get id >= that fromId. Otherwise most recent orders are returned.

The time between startTime and endTime can't be longer than 24 hours. These are the supported combinations of all parameters:

symbol

symbol + orderId

symbol + startTime

symbol + endTime

symbol + fromId

symbol + startTime + endTime

symbol+ orderId + fromId

Weight(IP): 20

get/api/v3/myTrades

Query parameters

symbolstring required

Example:BNBUSDT

Trading symbol, e.g. BNBUSDT

orderIdinteger

This can only be used in combination with symbol.

startTimeinteger

UTC timestamp in ms

endTimeinteger

UTC timestamp in ms

fromIdinteger

Trade id to fetch from. Default gets most recent trades.

limitinteger

Example:5

Default 500; max 1000.

recvWindowinteger

Example:5000

The value cannot be greater than 60000

timestampinteger required

UTC timestamp in ms

signaturestring required

Signature

Response

List of trades

symbolstring required

idinteger required

Trade id

orderIdinteger required

orderListIdinteger required

pricestring required

Price

qtystring required

Amount of base asset

quoteQtystring required

Amount of quote asset

commissionstring required

commissionAssetstring required

timeinteger required

Trade timestamp

isBuyerboolean required

isMakerboolean required

isBestMatchboolean required

Example response

[
  {
    "symbol": "BNBBTC",
    "id": 28457,
    "orderId": 100234,
    "orderListId": -1,
    "price": "4.00000100",
    "qty": "12.00000000",
    "quoteQty": "48.000012",
    "commission": "10.10000000",
    "commissionAsset": "BNB",
    "time": 1499865549590
  }
]

Changes

Changed in 1 of the 26 revisions of this API.717

Oct 25, 2021a484ce871a72717See the full diff
- ▲
  for the query request parameter endTime, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter fromId, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter limit, the type/format was changed from integer/ to integer/int32
  request-parameter-type-changed
- ▲
  for the query request parameter orderId, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter recvWindow, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter startTime, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ▲
  for the query request parameter timestamp, the type/format was changed from integer/ to integer/int64
  request-parameter-type-changed
- ○
  the response property code became required for the status 400
  response-property-became-required
- ○
  the response property code became required for the status 401
  response-property-became-required
- ○
  the response property items/commission became required for the status 200
  response-property-became-required
- ○
  the response property items/commissionAsset became required for the status 200
  response-property-became-required
- ○
  the response property items/id became required for the status 200
  response-property-became-required
- ○
  the response property items/isBestMatch became required for the status 200
  response-property-became-required
- ○
  the response property items/isBuyer became required for the status 200
  response-property-became-required
- ○
  the response property items/isMaker became required for the status 200
  response-property-became-required
- ○
  the response property items/orderId became required for the status 200
  response-property-became-required
- ○
  the response property items/orderListId became required for the status 200
  response-property-became-required
- ○
  the response property items/price became required for the status 200
  response-property-became-required
- ○
  the response property items/qty became required for the status 200
  response-property-became-required
- ○
  the response property items/quoteQty became required for the status 200
  response-property-became-required
- ○
  the response property items/symbol became required for the status 200
  response-property-became-required
- ○
  the response property items/time became required for the status 200
  response-property-became-required
- ○
  the response property msg became required for the status 400
  response-property-became-required
- ○
  the response property msg became required for the status 401
  response-property-became-required

Full history