Bitget ping
Keeps a connection alive. It is the plain string ping, not JSON, and the server answers with the string pong. Bitget recommends sending it every 30 seconds and says the server disconnects after 2 minutes without one.
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.
This is a message of the Bitget WebSocket API, not an HTTP endpoint. It has no method and no path: it is sent as JSON over an open WebSocket connection.
The same section says a connection accepts up to 10 messages a second, counting ping, login, subscribe and unsubscribe, and that a connection sending more is disconnected. Where no pong comes back, it says to reconnect.
The message
- Name
- ping
- Direction
- Request, sent by the client
- Carried by
- WebSocket. Sent on any connection. The addresses are the ones on Bitget's quick start page (bitget.com/docs/uta/quick-start), opened the same day, which also lists VIP and low latency hosts.
- Public channel
- wss://ws.bitget.com/v3/ws/public
- Public channel, demo trading
- wss://wspap.bitget.com/v3/ws/public
- Private channel
- wss://ws.bitget.com/v3/ws/private
- Private channel, demo trading
- wss://wspap.bitget.com/v3/ws/private
Fields
No fields are recorded for this message.
What arrives
pong: The plain string pong.
Limits that apply at Bitget
| 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 |