[ad_1]
Darius Baruo
Aug 06, 2024 07:32
Binance declares vital updates to its API, together with Request Weight Changes and WebSocket Consumer Knowledge Requests, efficient from September 3, 2024.
Binance, one of many world’s main cryptocurrency exchanges, has introduced a major replace to its API, set to take impact on September 3, 2024, at 06:00 UTC. In response to a discover from Binance, the replace will embrace changes to Request Weight and the deprecation of sure WebSocket Consumer Knowledge Requests.
Key Modifications
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 varied API endpoints. The specifics of those adjustments weren’t detailed within the announcement, however customers are suggested to seek advice from the up to date API documentation for full particulars.
2. Deprecation of WebSocket Consumer Knowledge Requests
Additionally efficient from September 3, 2024, a number of WebSocket Consumer Knowledge Requests might be deprecated. Customers are inspired to transition to the up to date model endpoints to learn from improved efficiency and performance.
Advisable Actions
Binance has supplied a set of latest endpoints for each REST and WebSocket APIs to interchange the deprecated ones. Listed here are the important thing updates:
REST API
New Endpoints to Question Account Data:
GET /fapi/v1/symbolConfig: Question consumer image configuration.
GET /fapi/v1/accountConfig: Question consumer account configuration.
GET /fapi/v3/account: Alternative of GET /fapi/v2/account. This endpoint solely returns symbols that the consumer has positions or open orders in. Configuration-related fields have been eliminated and might now be queried from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V3 endpoint additionally presents higher efficiency.
GET /fapi/v3/stability: Alternative of GET /fapi/v2/stability. Question consumer account stability.
New Endpoints to Question Commerce Data:
GET /fapi/v3/positionRisk: Alternative of GET /fapi/v2/positionRisk. This endpoint solely returns symbols that the consumer has positions or open orders in. Configuration-related fields have been eliminated and might 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 consumer has positions or open orders in. Configuration-related fields have been eliminated and might now be queried from GET /fapi/v1/symbolConfig and GET /fapi/v1/accountConfig. The V2 endpoint additionally presents higher efficiency.
v2/account.stability: Alternative of account.stability. Question consumer account stability.
v2/account.place: Alternative of account.place. This endpoint solely returns symbols that the consumer has positions or open orders in. Configuration-related fields have been eliminated and might now be queried from GET /fapi/v1/symbolConfig. The V2 endpoint additionally presents higher efficiency.
Binance emphasizes that customers ought to seek advice from the unique model of the announcement in English for probably the most correct info. 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 knowledge dealing with for its customers.
Picture supply: Shutterstock
[ad_2]
Source link
