.png)
Bybit • Latest Bybit News
Tags: News
Starting August 13, 2025, Bybit will roll out a new institutional API rate limit framework designed to enhance performance for high-frequency trading clients. The new system introduces a centralized institution-level rate cap with flexible per-UID configurations, enabling greater efficiency and scalability.
Key highlights
Centralized institution-level cap
- Each institution will receive a total RPS (requests per second) quota per business line. Example: 60,000 RPS for Futures, Options and Spot under Pro 6.
Flexible per-UID allocation
Institutions can assign higher RPS values to specific UIDs within the overall quota. Example: 1,200+ RPS per UID.
Full self-service control
- Rate limits per UID can be configured directly by institutions through a dedicated interface.
Why this matters
Legacy challenges
- Per-UID rate limit bottlenecks (e.g. 300 RPS)
- Required subaccount sprawl for scaling
- Fragmented capital across accounts
New benefits
- Increase rate limits for specific UIDs without opening extra accounts
- Fewer subaccounts, streamlined operations
- Improved capital efficiency and simplified fund management
Rate limit architecture
Business line rate caps are managed independently:
- Futures: Up to 60,000 RPS
- Options: Up to 60,000 RPS
- Spot: Up to 60,000 RPS
Default UID limits (non-counted):
- Futures/Options: 10 RPS
- Spot: 20 RPS
Current Status: | Post-Requirement (Per-UID Level): | Post-Requirement (Parent-Sub Account Level): | |||||||
UTA and UTA-Pro API Rate Limit (per UID level) | UTA and UTA-Pro API Rate Limit (per UID level) | UTA and UTA-Pro API Rate Limit (Institution level) | |||||||
Level | Futures | Option | Spot | Futures | Option | Spot | Futures | Option | Spot |
Default | 10/s | 10/s | 20/s | 10/s | 10/s | 20/s | n.a | n.a | n.a |
Pro1 | 150/s | 150/s | 150/s | 200/s | 200/s | 200/s | 10,000/s | 10,000/s | 10,000/s |
Pro2 | 200/s | 200/s | 200/s | 400/s | 400/s | 400/s | 20,000/s | 20,000/s | 20,000/s |
Pro3 | 250/s | 250/s | 250/s | 600/s | 600/s | 600/s | 30,000/s | 30,000/s | 30,000/s |
Pro4 | 300/s | 300/s | 300/s | 800/s | 800/s | 800/s | 40,000/s | 40,000/s | 40,000/s |
Pro5 | 300/s | 300/s | 300/s | 1,000/s | 1,000/s | 1,000/s | 50,000/s | 50,000/s | 50,000/s |
Pro6 | 300/s | 300/s | 300/s | 1,200/s | 1,200/s | 1,200/s | 60,000/s | 60,000/s | 60,000/s |
Configuration rules
Per-UID limit logic
Each UID can be assigned a custom request-per-second (RPS) value ranging from 10 RPS up to the maximum allowed by the institution’s tier (for example, 1,200 RPS).
The allocation follows this logic:
Final RPS = Max (Min (user-defined value, tier max), default limit)
Default UIDs (set at 10 RPS for Futures/Options and 20 RPS for Spot) are not counted toward the institution-level cap.
Remaining cap calculation
The remaining capacity available to an institution is calculated as:
Remaining capacity = Institution cap – Sum of all non-default UID RPS values
Downgrade/Upgrade Scenarios
Example 1: Upgrade from Pro 5 to Pro 6
- Institution-level cap increases from 50,000 RPS to 60,000 RPS
- Maximum per-UID allocation increases from 1,000 RPS to 1,200 RPS
Example 2: Downgrade from Pro 6 to Pro 5 (Auto throttling applied)
Initial setup:
- Total configured RPS: 300,000
- New Pro 5 institution cap: 50,000 RPS
Adjustment steps:
- Throttling ratio = 50,000 Ă· 300,000 = 16.67%
- All configured UID RPS values are scaled down proportionally using the throttling ratio
- Final total RPS = 50,000, fully aligned with the downgraded tier limit
Force Execution Date:
Starting September 15, we will begin enforcing the new API rate limits in accordance with the updated rules.
Thank you for choosing Bybit.
The Bybit Team
Source: Bybit Official Announcement — originally published on Tue, 15 Jul 2025 10:00:00 GMT.
