Binance to Implement Major API Updates in September 2024

0


Darius Baruo
Aug 06, 2024 07:32

Binance announces significant updates to its API, including Request Weight Adjustments and WebSocket User Data Requests, effective from September 3, 2024.





Binance, one of the world’s leading cryptocurrency exchanges, has announced a significant update to its API, set to take effect on September 3, 2024, at 06:00 UTC. According to a notice from Binance, the update will include adjustments to Request Weight and the deprecation of certain WebSocket User Data Requests.

Key Changes

The upcoming changes will primarily focus on two areas:

1. Request Weight Adjustments

Effective from September 3, 2024, Binance will implement changes to the Request Weight for various API endpoints. The specifics of these changes were not detailed in the announcement, but users are advised to refer to the updated API documentation for full details.

2. Deprecation of WebSocket User Data Requests

Also effective from September 3, 2024, several WebSocket User Data Requests will be deprecated. Users are encouraged to transition to the updated version endpoints to benefit from improved performance and functionality.

Recommended Actions

Binance has provided a set of new endpoints for both REST and WebSocket APIs to replace the deprecated ones. Here are the key updates:

REST API

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.

WebSocket API

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.

Binance emphasizes that users should refer to the original version of the announcement in English for the most accurate information. For further clarification and assistance, users can consult the API documentation or contact Binance Customer Service.

This update is part of Binance’s ongoing efforts to enhance its API services, ensuring better performance and more efficient data handling for its users.

Image source: Shutterstock


Credit: Source link

Leave A Reply

Your email address will not be published.