![]() ![]() for all market liquidation order streams.New endpoint GET /fapi/v1/allForceOrders to get all liquidation orders.reduceOnly has been supported in orders with type:.New endpoint DELETE /fapi/v1/batchOrders to cancel a list of open orders.New endpoint DELETE /fapi/v1/allOpenOrders to cancel all open orders of a specific symbol.New field in response to GET /fapi/v1/accountrelated to isolated position: isolated New field in response to GET /fapi/v1/positionRisk related to isolated position: Faster diff data with real time updates: endpoints related to isolated position:.New SDK and Code Demonstration on Python."cumQty" is going to be removed from the responses to DELETE /fapi/v1/order, DELETE /fapi/v1/batchOrders and other order relatived endpoints in the coming weeks.New market data endpoint GET /fapi/v1/leverageBracket to check notional and leverage brackets.created time + 30 days and New diff depth data with 500ms updates: New partial depth data with 500ms updates: New SDK and Code Demonstration on Java.order status is CANCELED or EXPIRED, AND.Some orders that were cancelled/expired will be removed gradually from API endpoints, but they are still available from Web UI. New fields in payloads of and !bookTicker:.New field closePosition in response to endpoints: If a STOP_MARKET or TAKE_PROFIT_MARKET order with closePosition=true is triggered,all of the current long position( if SELL order) or current short position( if BUY order) will be closed. New parameter closePosition for endpoint POST /fapi/v1/order: Better performance than the v1 endpoint.Different responses for "One-way" or "Hedge" position mode.All symbols in the market can be returned.User can choose to send specific "symbol".New endpoint GET /fapi/v2/positionRisk in version 2 of fapi:.New endpoints of version 2 of fapi, having better performance than the v1 endpoints:. ![]() New fields in responses to GET /fapi/v2/account and GET /fapi/v2/balance:.New field "rp" for the realized profit of the trade in event "ORDER_TRADE_UPDATE".New field "m" for event reason type in event "ACCOUNT_UPDATE".Weights of endpoint GET /fapi/v1/income has been changed as 20.New endpoint GET /fapi/v1/adlQuantile to get the positions' ADL quantile estimation values.New endpoint GET /fapi/v1/forceOrders to get the user's force orderes.New field "i" for indexPrice in payload of ws streams:.New field "indexPrice" in response to endpoint GET /fapi/v1/premiumIndex.New endpoint GET /fapi/v1/indexInfo to get information of composite index.New WebSocket streams for composite index symbol information.Please visit here to get examples for helping to understand the upgrade. In short, the full information of assets and positions should be obtained via the related RESTful endpoints( GET /fapi/v2/account and GET /fapi/v2/positionRisk), and the locally cached asset or position data can be updated via the event ACCOUNT_UPDATE in Websocket USER-DATA-STREAM with the information of changed asset or position. Position information of other symbols will no longer be pushed, even their positions may not be 0.Initialized "LONG" or "SHORT" isolated position of this symbol will also be pushed.If the change happens in "LONG" or "SHORT" position, the changed "LONG" or "SHORT" position of this symbol will be pushed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |