Binance to Implement Major API Updates in September 2024

Binance, one of many world’s main cryptocurrency exchanges, has introduced a big replace to its API, set to take impact on September 3, 2024, at 06:00 UTC. Based on a discover from Binance, the replace will embody changes to Request Weight and the deprecation of sure WebSocket Consumer Information Requests.

Key Adjustments

The upcoming adjustments will primarily concentrate on two areas:

1. Request Weight Changes

Efficient from September 3, 2024, Binance will implement adjustments to the Request Weight for numerous API endpoints. The specifics of those adjustments weren’t detailed within the announcement, however customers are suggested to consult with the up to date API documentation for full particulars.

2. Deprecation of WebSocket Consumer Information Requests

Additionally efficient from September 3, 2024, a number of WebSocket Consumer Information Requests will probably be deprecated. Customers are inspired to transition to the up to date model endpoints to learn from improved efficiency and performance.

Really useful Actions

Binance has supplied a set of recent endpoints for each REST and WebSocket APIs to exchange the deprecated ones. Listed below are the important thing updates:

REST API

New Endpoints to Question Account Data:

• GET /fapi/v1/symbolConfig: Question person image configuration.

• GET /fapi/v1/accountConfig: Question person account configuration.

• GET /fapi/v3/account: Alternative of GET /fapi/v2/account. This endpoint solely returns symbols that the person has positions or open orders in. Configuration-related fields have been eliminated and may now be queried from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V3 endpoint additionally presents higher efficiency.

• GET /fapi/v3/steadiness: Alternative of GET /fapi/v2/steadiness. Question person account steadiness.

New Endpoints to Question Commerce Data:

• GET /fapi/v3/positionRisk: Alternative of GET /fapi/v2/positionRisk. This endpoint solely returns symbols that the person has positions or open orders in. Configuration-related fields have been eliminated and may now be queried from GET /fapi/v1/symbolConfig. The V3 endpoint additionally presents higher efficiency.

WebSocket API

New Endpoints to Question Account Data:

• v2/account.standing: Alternative of account.standing. This endpoint solely returns symbols that the person has positions or open orders in. Configuration-related fields have been eliminated and may now be queried from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V2 endpoint additionally presents higher efficiency.

• v2/account.steadiness: Alternative of account.steadiness. Question person account steadiness.

• v2/account.place: Alternative of account.place. This endpoint solely returns symbols that the person has positions or open orders in. Configuration-related fields have been eliminated and may now be queried from GET /fapi/v1/symbolConfig. The V2 endpoint additionally presents higher efficiency.

Binance emphasizes that customers ought to consult with the unique model of the announcement in English for essentially the most correct data. For additional clarification and help, customers can seek the advice of the API documentation or contact Binance Buyer Service.

This replace is a part of Binance’s ongoing efforts to boost its API providers, making certain higher efficiency and extra environment friendly information dealing with for its customers.

Picture supply: Shutterstock