Broker API
Bitget API: REST and WebSocket
A crypto exchange with a REST and WebSocket API of its own.
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.
Bitget API rate limits and allowances
One record per limit. The scope is part of the limit: a figure without its scope is not a figure you can pace against.
| Limit | Value | Scope | Source |
|---|---|---|---|
| Public market data, legacy v1 API | 20 per 2 s per IP, public market data | Per IP address, public market data endpoints of the legacy v1 API | bitgetlimited.github.iochecked |
| Overall requests a minute | 6,000 | Per IP address, all requests to the common domain name, with REST and WebSocket sharing one allowance | bitget.comchecked |
| Concurrent WebSocket connections | 100 | Per IP address | bitget.comchecked |
| WebSocket messages a second | 10 | Per WebSocket connection, counting ping, login, subscribe and unsubscribe messages | bitget.comchecked |
| WebSocket subscription requests an hour | 240 | Per WebSocket connection | bitget.comchecked |
| Concurrent WebSocket channel subscriptions | 1,000 | Per WebSocket connection | bitget.comchecked |
Bitget API rate limits in full, with pacing advice and the related error codes.
Access, authentication and streaming
API types listed in the record: REST, WebSocket.
- How you get a key
Log in to the Bitget website and create an API key under API Key Management. Each key set is an API key, a secret key and a passphrase you choose, with read or read and write permissions, and one UID can hold up to 50 key sets. Bitget recommends binding the key to an IP address.
Bitget API quick startchecked
- Demo
Yes: demo trading with virtual funds. Switch the account to Demo mode on the website, create a Demo API key there, then send REST requests to the usual host with the header paptrading set to 1. WebSocket demo trading has its own addresses on wspap.bitget.com.
- Authentication
Signed requests. Every REST request carries the headers ACCESS-KEY, ACCESS-SIGN, ACCESS-TIMESTAMP and ACCESS-PASSPHRASE. The signature is the timestamp, the upper case method, the request path, the query string and the body joined together, signed with HMAC SHA256 using the secret key (or with an RSA private key) and then Base64 encoded. For REST the page gives the timestamp in milliseconds since the epoch, and its sample code computes it that way. The WebSocket login is signed in a similar way, but Bitget's page is not consistent about its timestamp unit, so this record states none for it; the login message page sets out both readings.
- Streaming
WebSocket, with a public channel and a private channel that needs a login message. Stated on the quick start page: at most 100 connections per IP, 300 connection requests per IP in 5 minutes, at most 1,000 channel subscriptions per connection (Bitget advises fewer than 50), 240 subscription requests an hour per connection, and up to 10 messages a second per connection. Send the string ping every 30 seconds; the server disconnects after 2 minutes without one.
- 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.
Bitget API quick start, Rate Limitchecked Bitget API docs (legacy v1), frequency limiting ruleschecked
Bitget messages
10 documented messages and subscriptions of the Bitget WebSocket API. They are not HTTP endpoints: none has a method or a path, and each travels over a connection that stays open. Grouped by what they do, each with its summary
Bitget API SDKs and wrappers
| Library | Language | Official | Note | Source |
|---|---|---|---|---|
| bitget-java-sdk-api | Java | Official | Listed as an official SDK on Bitget's SDK page. The repository itself was not opened. | bitget.comchecked |
| bitget-python-sdk-api | Python | Official | Listed as an official SDK on Bitget's SDK page. The repository itself was not opened. | bitget.comchecked |
| bitget-node-sdk-api | Node.js | Official | Listed as an official SDK on Bitget's SDK page. The repository itself was not opened. | bitget.comchecked |
| bitget-golang-sdk-api | Go | Official | Listed as an official SDK on Bitget's SDK page. The repository itself was not opened. | bitget.comchecked |
| bitget-php-sdk-api | PHP | Official | Listed as an official SDK on Bitget's SDK page. The repository itself was not opened. | bitget.comchecked |
Bitget API: questions and answers
Each answer is read from the record on this page, not written separately. Where the record is unverified, the answer says so.
Does Bitget have an API?
Yes. This register records Bitget as having its own API (REST and WebSocket), with availability marked as active. A crypto exchange with a REST and WebSocket API of its own.
Bitget API introductionchecked
Bitget API key: how do I get one?
Log in to the Bitget website and create an API key under API Key Management. Each key set is an API key, a secret key and a passphrase you choose, with read or read and write permissions, and one UID can hold up to 50 key sets.
Bitget API quick startchecked
Bitget API demo: is there a demo or sandbox?
Yes: demo trading with virtual funds. Switch the account to Demo mode on the website, create a Demo API key there, then send REST requests to the usual host with the header paptrading set to 1. WebSocket demo trading has its own addresses on wspap.bitget.com.
What are the Bitget API rate limits?
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. 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. Concurrent WebSocket connections: 100 connections. Scope: Per IP address. WebSocket messages a second: 10 messages per second. Scope: Per WebSocket connection, counting ping, login, subscribe and unsubscribe messages. WebSocket subscription requests an hour: 240 subscription requests per hour. Scope: Per WebSocket connection. Concurrent WebSocket channel subscriptions: 1,000 channel subscriptions. Scope: Per WebSocket connection. As the record words it: 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.
bitgetlimited.github.iochecked bitget.comchecked
How does Bitget API authentication work?
Signed requests. Every REST request carries the headers ACCESS-KEY, ACCESS-SIGN, ACCESS-TIMESTAMP and ACCESS-PASSPHRASE.
Does the Bitget API support streaming?
WebSocket, with a public channel and a private channel that needs a login message.
Is there a Python library for the Bitget API?
This register lists one Python library for the Bitget API. bitget-python-sdk-api (official, Python): Listed as an official SDK on Bitget's SDK page. The repository itself was not opened.
bitget-python-sdk-apichecked
Bitget API questions, each answered in a sentence or two.
The capability tables read one feature at a time across every broker and platform record, Bitget included.
Everything this site records for Bitget, as one JSON file. Each section of the file states its own licence. About the files. This page as Markdown.
What changed recently for the Bitget API
Documentation
Bitget's current API documentation states an overall limit of 6,000 requests a minute per IP address, alongside per endpoint limits. This site previously held only the legacy v1 figure of 20 requests in 2 seconds for public market data.
Bitget API quick startchecked
Documentation
Bitget's quick start page gives the REST signing timestamp in milliseconds, but for the WebSocket login its text says milliseconds and its JavaScript sample uses milliseconds while its Java step divides by 1,000 and its example holds a ten digit value. This site's authentication entry for Bitget now keeps the milliseconds statement to REST and states no unit for the login, where it previously said only that the timestamp is in milliseconds.
Bitget API quick startchecked
Every dated change, all brokers and platforms. Follow Bitget changes by RSS
Partner programme
Not verified. No programme page could be opened at the last check, , which is not evidence that no programme exists. The Bitget partner programme record. The programme register holds every record. This site carries no affiliate links.
How to cite this
Bitget API: REST and WebSocket. Broker API Hub, https://openbrokerapi.com/brokers/bitget, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.