Fellow Binancians,
Binance will update the Request Weight Adjustments and WebSocket User Data Requests from 2024-09-03 06:00 (UTC).
Request Weight Adjustments (Effective from 2024-09-03)
Deprecation of WebSocket User Data Requests (Effective from 2024-09-03)
The following WebSocket User Data Requests will be deprecated:
<listenKey>@account:
USDⓈ-M Futures: Documentation
COIN-M Futures: Documentation
<listenKey>@balance:
USDⓈ-M Futures: Documentation
COIN-M Futures: Documentation
<listenKey>@position:
USDⓈ-M Futures: Documentation
COIN-M Futures: Documentation
For COIN-M Futures, users are still recommended to use existing API to query:
For USDⓈ-M Futures, users are encouraged to switch to the following updated version endpoints for improved performance and functionality.
New Endpoints to Query Account Information:
GET /fapi/v1/symbolConfig: Query user symbol configuration.
GET /fapi/v1/accountConfig: Query user account configuration.
GET /fapi/v3/account: Replacement of GET /fapi/v2/account. This endpoint only returns symbols that the user has positions or open orders in. Configuration-related fields have been removed and can now be queried from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V3 endpoint also offers better performance.
GET /fapi/v3/balance: Replacement of GET /fapi/v2/balance. Query user account balance.
New Endpoints to Query Trade Information:
GET /fapi/v3/positionRisk: Replacement of GET /fapi/v2/positionRisk. This endpoint only returns symbols that the user has positions or open orders in. Configuration-related fields have been removed and can now be queried from GET /fapi/v1/symbolConfig. The V3 endpoint also offers better performance.
New Endpoints to Query Account Information:
v2/account.status: Replacement of account.status. This endpoint only returns symbols that the user has positions or open orders in. Configuration-related fields have been removed and can now be queried from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V2 endpoint also offers better performance.
v2/account.balance: Replacement of account.balance. Query user account balance.
v2/account.position: Replacement of account.position. This endpoint only returns symbols that the user has positions or open orders in. Configuration-related fields have been removed and can now be queried from GET /fapi/v1/symbolConfig. The V2 endpoint also offers better performance.
Note: There may be discrepancies in the translated version of this original article in English. Please reference this original version for the latest or most accurate information where any discrepancies may arise.
We appreciate your understanding and cooperation as we work to enhance our services. For any questions or assistance, please refer to our API documentation or contact Binance Customer Service agents.
Thank you for your support!
Binance Team
2024-08-06
Note: This announcement was updated on 2024-08-29 to add API Doc redirect links and to emphasize that the deprecation of this interface applies to both USDⓈ-M and COIN-M Futures.
Trade on-the-go with Binance’s crypto trading app (iOS/Android)
Find us on
Binance reserves the right in its sole discretion to amend or cancel this announcement at any time and for any reasons without prior notice.
Disclaimer: Digital asset prices are subject to high market risk and price volatility. The value of your investment may go down or up, and you may not get back the amount invested. You are solely responsible for your investment decisions and Binance is not liable for any losses you may incur. Past performance is not a reliable predictor of future performance. You should only invest in products you are familiar with and where you understand the risks. You should carefully consider your investment experience, financial situation, investment objectives and risk tolerance and consult an independent financial adviser prior to making any investment. This material should not be construed as financial advice. For more information, see our Terms of Use and Risk Warning.