# Bitget API rate limits Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade. This is the markdown version of https://openbrokerapi.com/brokers/bitget/rate-limits, written from the same records as that page. Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders. What is recorded about how fast you may call the Bitget API: 6 limit records, the wording from the record and no related error code yet. - Newest check: 2026-10-12 ## Recorded limits One record per limit. The scope is part of the limit: a figure is only useful once you know whether it applies to a key, an account, a session or an address. - Public market data, legacy v1 API: 20 per 2 s per IP, public market data - Scope: Per IP address, public market data endpoints of the legacy v1 API - Status: verified. Source: [bitgetlimited.github.io](https://bitgetlimited.github.io/apidoc/en/spot/), checked 2026-10-12. - Note: Re-read on the legacy v1 documentation on 12 Oct 2026: 20 requests in 2 seconds. Authenticated endpoints there are set per endpoint per UID, and a general endpoint with no figure of its own is 10 a second. HTTP 429 on breach. The window is 2 seconds, which a single unit cannot state, so the figure stays as wording. The current API states its own overall limit, held in a separate record. - Overall requests a minute: 6,000 requests per minute - Scope: Per IP address, all requests to the common domain name, with REST and WebSocket sharing one allowance - Status: verified. Source: [bitget.com](https://www.bitget.com/docs/uta/quick-start), checked 2026-10-12. - Note: Each endpoint also carries its own limit on its own documentation page, counted separately. HTTP 429 on breach. - Concurrent WebSocket connections: 100 connections - Scope: Per IP address - Status: verified. Source: [bitget.com](https://www.bitget.com/docs/uta/quick-start), checked 2026-10-12. - Note: Also 300 connection requests per IP in 5 minutes. - WebSocket messages a second: 10 messages per second - Scope: Per WebSocket connection, counting ping, login, subscribe and unsubscribe messages - Status: verified. Source: [bitget.com](https://www.bitget.com/docs/uta/quick-start), checked 2026-10-12. - Note: A connection that sends more is disconnected, and an IP that is disconnected repeatedly may be blocked. - WebSocket subscription requests an hour: 240 subscription requests per hour - Scope: Per WebSocket connection - Status: verified. Source: [bitget.com](https://www.bitget.com/docs/uta/quick-start), checked 2026-10-12. - Concurrent WebSocket channel subscriptions: 1,000 channel subscriptions - Scope: Per WebSocket connection - Status: verified. Source: [bitget.com](https://www.bitget.com/docs/uta/quick-start), checked 2026-10-12. - Note: Bitget recommends fewer than 50 channels on one connection. ## Rate limits, as the record words them - Rate limits, as worded: The quick start page for the current API states an overall limit of 6,000 requests a minute per IP on the common domain name, with each endpoint also carrying its own limit on its own documentation page, counted separately. REST and WebSocket share one allowance, and a breach returns HTTP 429. The response header x-mbx-used-remain-limit reports what is left for the endpoint called. Bitget's legacy v1 documentation, still published, states 20 requests in 2 seconds for public market data and 10 a second for a general endpoint with no figure of its own. - Status: verified. Source: [Bitget API quick start, Rate Limit](https://www.bitget.com/docs/uta/quick-start), checked 2026-10-12. - Status: verified. Source: [Bitget API docs (legacy v1), frequency limiting rules](https://bitgetlimited.github.io/apidoc/en/spot/), checked 2026-10-12. ## Error codes that concern limits Not recorded: no decoded Bitget error names a rate limit yet. ## Pacing and backoff, in general This part is general advice and says nothing about Bitget in particular. The figures that apply are the recorded ones above, and the provider's own documentation is the authority. Pace before you are refused. Work out the gap between requests that keeps you under the limit, then leave a margin, because a limit counted by a provider's clock will not line up exactly with yours. Spread calls evenly: a burst at the start of each window is the usual way to hit a limit while staying under it on average. The rate limit calculator at https://openbrokerapi.com/tools/rate-limit-calculator checks a polling plan against a limit and gives the shortest interval that fits. When a request is refused for rate, stop sending and wait. Double the wait after each refusal in a row, add a small random amount so that several programs do not retry together, and cap the number of attempts. If the reply names how long to wait, use that figure in place of your own. Take extra care with dealing requests. A refused or unanswered order may or may not have gone through, so check the state of the order before you send it again. Cache what does not change, such as instrument details and history you have already downloaded, and prefer a stream to polling where one is offered. ## Where to go next - [The full Bitget record](https://openbrokerapi.com/brokers/bitget) - [Rate limits for every broker and platform](https://openbrokerapi.com/rate-limits) - [The fact register](https://openbrokerapi.com/facts) ## Licence and how to cite The limit records on this page come from the limits register, which is CC BY 4.0 (https://openbrokerapi.com/data/limits.json). Everything else on it comes from records that are all rights reserved. This file is the page itself, at its own address, in another format, and it is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Cite as: Bitget API rate limits. Broker API Hub, https://openbrokerapi.com/brokers/bitget/rate-limits, newest check 2026-10-12. Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.