$BNB $ETH $BTC Fellow Binancians,

Binance will update the Request Weight Adjustments and WebSocket User Data Requests from 2024-09-03 06:00 (UTC).

Key Changes

1. Request Weight Adjustments (Effective from 2024-09-03)

REST API

WebSocket API

Current

New

GET /fapi/v2/balance

account.balance

5

10

GET /fapi/v2/account

account.status

GET /fapi/v2/positionRisk

account.position

2. Deprecation of WebSocket User Data Requests (Effective from 2024-09-03)

The following WebSocket User Data Requests will be deprecated:

@account: Documentation

@balance: Documentation

@position: Documentation

Recommended Actions

Users are encouraged to switch to the updated version endpoints for improved performance and functionality.

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