Key Updates to Binance API 🚀
Binance, a major player in the cryptocurrency exchange world, has announced significant changes to its API set to be implemented on September 3, 2024, at 06:00 UTC. The updates include adjustments to Request Weight and the deprecation of certain WebSocket User Data Requests.
Primary Modifications 🔧
1. Request Weight Adjustments
- Starting September 3, 2024, Binance will make changes to the Request Weight for various API endpoints. The specifics of these adjustments were not provided in the announcement.
2. Deprecation of WebSocket User Data Requests
- Effective September 3, 2024, several WebSocket User Data Requests will no longer be supported. Users are urged to shift to the updated version endpoints to enjoy enhanced performance and features.
Actions to Consider 👩💻
Binance has introduced new endpoints for both REST and WebSocket APIs to substitute the outdated ones. Here are the key updates:
REST API
- New Endpoints to Query Account Information:
- GET /fapi/v1/symbolConfig: Retrieve user symbol configuration.
- GET /fapi/v1/accountConfig: Fetch user account configuration.
- GET /fapi/v3/account: An upgrade of GET /fapi/v2/account, this endpoint now provides symbols the user has positions or open orders in. Configuration-related fields can be accessed from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V3 endpoint also offers improved performance.
- GET /fapi/v3/balance: Replaces GET /fapi/v2/balance. Query user account balance.
- New Endpoints to Query Trade Information:
- GET /fapi/v3/positionRisk: Substitution for GET /fapi/v2/positionRisk. This endpoint only returns symbols the user has positions or open orders in. Configuration-related information can now be obtained from GET /fapi/v1/symbolConfig. The V3 endpoint also provides better performance.
WebSocket API
- New Endpoints to Query Account Information:
- v2/account.status: Replaces account.status. This endpoint now only displays symbols the user has positions or open orders in. Configuration-related fields can be accessed from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V2 endpoint also offers better performance.
- v2/account.balance: Substitution for account.balance. Query user account balance.
- v2/account.position: Replaces account.position. This endpoint only returns symbols the user has positions or open orders in. Configuration-related fields can be accessed from GET /fapi/v1/symbolConfig. The V2 endpoint also offers better performance.
Binance recommends referring to the original English version of the announcement for the most precise information. For additional support, users can consult the API documentation or contact Binance Customer Service. This update reflects Binance’s continuous drive to improve its API services, ensuring enhanced performance and more effective data management for users.
Hot Take 🌶️
Stay informed and adapt to the latest changes in the Binance API for seamless trading experiences. Remember to make the necessary adjustments before the implementation date to avoid any disruptions in your trading activities. Embrace these updates to optimize your use of Binance’s API and leverage the improved features for a smoother crypto trading journey. Keep evolving with Binance’s enhancements for a more efficient and effective trading experience!
By
By
By
By
By