Effective from August 25, 2023, Binance implemented significant changes to its Spot API request weight limits to enhance the trading experience for API users. 

Key Updates:

1. Increased Request Weight Limit per IP Address:

• The shared request weight limit per IP address across all endpoints was raised from 1,200 to 6,000 per minute. 

2. Endpoint-Specific Request Weight Adjustments:

• Order Placement and Cancellation Endpoints:

• The request weight for these endpoints remained unchanged. However, due to the increased overall limit, a single IP can now send up to five times more requests to these endpoints than before. 

• Other Endpoints:

• The request weight for all other endpoints was doubled. Consequently, a single IP can now send up to 2.5 times more requests to these endpoints. 

Understanding Request Weight:

Each API request carries a specific weight, reflecting the system resources it consumes. For instance, fetching depth information for a symbol with a limit of 5 levels has a weight of 1, while fetching with a limit of 5,000 levels has a weight of 50.  It’s crucial to monitor your API usage to avoid exceeding the allocated weight limits.

Recommendations for API Users:

• Update API Settings:

• To align with the new limits, users should adjust their API configurations. The /api/v3/exchangeInfo endpoint provides current rate limit details. 

• Monitor Weight Usage:

• Keep track of your request weight consumption using the X-MBX-USED-WEIGHT-1M and X-MBX-USED-WEIGHT headers in API responses. 

• Adhere to Rate Limits:

• Exceeding the request weight limit can result in HTTP status code 429 responses, indicating the need to reduce request frequency. Persistent violations may lead to IP bans, with status code 418 indicating such bans. 

These adjustments aim to provide a more efficient and reliable trading environment for all Binance Spot API users.