Bitget messages
10 documented messages of the Bitget WebSocket API, grouped by what they do. Each has its fields, what arrives and the source it was read from.
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.
These are messages and subscriptions carried by a connection that stays open, not HTTP endpoints: none has a method or a path. For that reason they are in no OpenAPI file on this site and the request builder does not list them. A message that is not listed is not recorded here, which is not evidence that it does not exist.
Connection
2 messages
- loginLogs a WebSocket connection in, so that private channels can be subscribed to. It carries the API key, its passphrase, a timestamp and a signature of that timestamp made with the secret key. Bitget says a failed login disconnects the connection.
- pingKeeps 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.
Private channels
4 messages
- accountThe unified trading account: equity, margin figures and the balance of each coin. Bitget says data is pushed on first subscribing, when orders are filled, when funds are settled and when a balance changes.
- fillThe fills of the unified trading account in real time. Bitget says nothing is pushed on first subscribing, and that a push follows when a spot, leveraged or futures order is filled.
- orderThe orders of the unified trading account. Bitget says nothing is pushed on first subscribing, and that a push follows when a spot, margin or futures order is placed, filled or cancelled.
- positionThe positions of the unified trading account. Bitget says data is pushed on first subscribing, and then incrementally when futures positions are opened or closed and when orders that close a position are placed, changed or cancelled.
Public channels
4 messages
- booksOrder book depth for one symbol. The topic chooses the depth: books for every level, books1 for 1, books5 for 5 and books50 for 50. books and books50 send a snapshot first and then incremental updates, while books1 and books5 send a snapshot every time.
- klineCandlesticks for one symbol at one interval. Bitget says data is pushed once a second while there are trades, and once per interval when there are none.
- publicTradeThe public trades of one symbol, pushed in real time: the price, the size, the side and the time of each fill.
- tickerThe latest price of one symbol with its best bid and ask and its 24 hour figures. Bitget says updates are pushed every 200 ms while the market is changing.