Sign in
Market

Compressed/Aggregate Trades List

Get compressed, aggregate trades. Trades that fill at the time, from the same order, with the same price will have the quantity aggregated.

  • If fromId, startTime, and endTime are not sent, the most recent aggregate trades will be returned.

  • Note that if a trade has the following values, this was a duplicate aggregate trade and marked as invalid:

    p = '0' // price

    q = '0' // qty

    f = -1 // first_trade_id

    l = -1 // last_trade_id

Weight(IP): 2

get/api/v3/aggTrades

Query parameters

symbolstring required
Example:BNBUSDT

Trading symbol, e.g. BNBUSDT

fromIdinteger

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

startTimeinteger

UTC timestamp in ms

endTimeinteger

UTC timestamp in ms

limitinteger
Example:5

Default 500; max 1000.

Response

Trade list

ainteger required

Aggregate tradeId

pstring required

Price

qstring required

Quantity

finteger required

First tradeId

linteger required

Last tradeId

Tboolean required

Timestamp

mboolean required

Was the buyer the maker?

Mboolean required

Was the trade the best price match?

Example response

[
  {
    "a": 26129,
    "p": "0.01633102",
    "q": "4.70443515",
    "f": 27781,
    "l": 27781
  }
]

Changes

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

  • a484ce871a72410See 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 startTime, 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 items/M became required for the status 200

      response-property-became-required

    • ○

      the response property items/T became required for the status 200

      response-property-became-required

    • ○

      the response property items/a became required for the status 200

      response-property-became-required

    • ○

      the response property items/f became required for the status 200

      response-property-became-required

    • ○

      the response property items/l became required for the status 200

      response-property-became-required

    • ○

      the response property items/m became required for the status 200

      response-property-became-required

    • ○

      the response property items/p became required for the status 200

      response-property-became-required

    • ○

      the response property items/q became required for the status 200

      response-property-became-required

    • ○

      the response property msg became required for the status 400

      response-property-became-required