The /dapi/v1/exchangeInfo rateLimits array contains objects related to the exchange's RAW_REQUEST, REQUEST_WEIGHT, and ORDER rate limits.If a parameter sent in both the query string and request body, the.Query string and request body if you wish to do so. Query string or in the request body with content typeĪpplication/x-www-form-urlencoded. For POST, PUT, and DELETE endpoints, the parameters may be sent as a.For GET endpoints, parameters must be sent as a query string.Specific error codes and messages defined in Error Codes.The regular expression rule for newClientOrderId updated as ^ Following endpoints' weights will be updated to 20 with symbol and 50 without symbol:.The query time period for endpoint GET /dapi/v1/allForceOrders must be less than 7 days (default as the recent 7 days).The endpoint GET /dapi/v1/allForceOrders stop being maintained and no longer accepts request.Instead, they push snapshot order data at a maximum frequency of 1 order push per second.: The following liquidation orders streams do not push realtime order data anymore.New field 'bc' for balance change in event 'ACCOUNT_UPDATE'.'marketTakeBound' for he max price difference rate( from mark price) a market order can make.'liquidationFee' for liquidation fee rate.New fields in the response of GET /dapi/v1/exchangeInfo:.New field updateTime as last update time of asset and position in response of GET /dapi/v1/account and GET /dapi/v1/positionRisk.New type 'AMENDMENT' as order modify in Execution Type x of Order Update event ORDER_TRADE_UPDATE.New endpoint GET /dapi/v1/orderAmendment to get order modify history.New endpoints PUT /dapi/v1/order and PUT /dapi/v1/batchOrders to support limit order modify.New field positionAmt as position amount in response of GET /dapi/v1/account.

The maximum value of limit in GET /dapi/v1/userTrades is adjusted to 1000.

Binance desktop client full screen