Binance will adjust the request weights for several Rest API interfaces starting April 28, 2021, at 08:00 (HKT). Below are the changes:
| Interface | Previous Request Weight | Updated Request Weight |
|----------------------------|-------------------------|-------------------------|
| GET /api/v3/order | 1 | 2 |
| GET /api/v3/openOrder | 1 | 3 |
| GET /api/v3/allOrders | 5 | 10 |
| GET /api/v3/orderList | 1 | 2 |
| GET /api/v3/openOrderList| 2 | 3 |
| GET /api/v3/account | 5 | 10 |
| GET /api/v3/myTrades | 5 | 10 |
| GET /api/v3/exchangeInfo | 1 | 10 |
👉 Learn how to optimize your API usage
For details, refer to Binance’s API documentation and Rest API documentation.
Key Takeaways
- Increased Efficiency: Higher request weights may impact high-frequency traders.
- Resource Allocation: Adjustments aim to balance server load and user access.
- Planning Ahead: Users should review their integration scripts for compliance.
FAQs
Q: Why is Binance changing API request weights?
A: To optimize server performance and ensure equitable resource distribution.
Q: Will this affect my trading bots?
A: Yes, if your bots exceed rate limits. Monitor performance post-update.
Q: How can I check my current API usage?
A: Use Binance’s GET /api/v3/rateLimit/order endpoint.
👉 Explore Binance’s latest API enhancements
Risk Warning: Cryptocurrency trading involves high risks. Binance does not guarantee compensation for losses. Always assess market conditions before trading.
Stay updated with Binance’s official announcements for further changes.
### Keywords:
- Binance API
- Rest API adjustments
- Request weight
- Cryptocurrency trading
- API documentation
- Rate limits
- High-frequency trading
- Server optimization
### Notes:
- Removed promotional links, dates, and non-essential navigation.
- Structured content with Markdown for SEO clarity.
- Anchors link exclusively to `https://www.okx.com/join/BLOCKSTAR` per guidelines.