Bitget Institutional API Raises Single-Account Ceiling to 600 RPS, Adds 120,000 RPS Aggregate Cap
VICTORIA, SEYCHELLES, September 3rd, 2026, Chainwire
Bitget’s updated institutional API rate-limit framework takes effect today, raising the top configurable single-account ceiling to 600 requests per second (RPS) per UID for eligible market-maker (MM1) and PRO-tier (PRO6) clients trading under Bitget’s unified trading account (UTA). The framework also introduces an aggregate master-sub-account rate-limit cap of up to 120,000 RPS, separately quoted for UTA spot and UTA futures trading.
The 600 RPS ceiling applies only to the top MM1 and PRO6 tiers; other market-maker and PRO tiers receive correspondingly lower single-account and aggregate caps, and classic-account mode rate limits are unchanged. The maximum ceiling is not applied automatically — institutions must configure quotas per UID according to their trading strategy and account structure, and the combined allocation across sub-accounts cannot exceed the aggregate cap for that tier.
Sub-accounts created after initialization require manual rate-limit configuration; where no quota is set, Bitget’s published framework applies a default limit of 10 requests per second once the mechanism takes effect. Bitget has advised existing eligible users to complete configuration ahead of the effective date to avoid falling back to the default.
Why Rate Limits Matter for Market Makers
API rate limits determine how frequently an automated trading system can submit, cancel and replace orders, pull account data and manage execution workflow without being throttled. For market makers quoting across multiple instruments or operating several sub-accounts, a higher, more granular per-UID ceiling reduces the need to spread activity across additional accounts simply to gain request capacity — Bitget states the new structure lets institutions raise limits for a specific UID without opening new accounts.
The update sits inside Bitget’s wider institutional stack, which covers unified trading accounts, whitelisted sub-account and API management, block trade and OTC — positioning Bitget at the execution layer of an institutional setup rather than as a custodian. Institutional users typically pair execution access at a venue like Bitget with custody held through separate arrangements, a multi-provider structure common across the industry.
Scope and Configuration
The framework applies to MM and PRO users trading spot and futures through Bitget’s unified trading account. Technical documentation covering API authentication, endpoint-level rate limits and unified-account integration is available in Bitget’s API documentation. Institutional account setup, including sub-account creation and API permissioning, is covered in Bitget’s unified trading account guide.
Institutional clients seeking access to PRO-tier services or assistance with API configuration can contact Bitget’s Institutional Partnerships team at institutional@bitget.com.
About Bitget
Founded in 2018 and registered in Seychelles, Bitget is a global cryptocurrency exchange positioned as a Universal Exchange (UEX), bringing crypto and a growing range of tokenized and traditional-market trading products into a unified platform. Bitget’s institutional offering includes unified trading accounts, sub-account and API management, PRO-tier services and institutional lending.
Bitget has published monthly proof-of-reserves data since December 2022 and maintains a separate Protection Fund — a discretionary corporate reserve held apart from user deposits.
For more information, visit bitget.com.