Bitget fill

messagefillBitget WebSocket APIWebSocketPrivate channels

The 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.

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.

Independent and unofficialbitget.comchecked 12 Oct 2026

This is a subscription 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 message

Name: fill
Direction: Subscription, opened by the client and then fed by the server
Subscribed to as: fill
Carried by: WebSocket. This channel is in the private section of Bitget's WebSocket documentation, so the connection has to send login first. 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.
Private channel: wss://ws.bitget.com/v3/ws/private
Private channel, demo trading: wss://wspap.bitget.com/v3/ws/private

Fields

The vendor's page does not say which of these fields are required or always present.

Name	Type	Description
op	String	subscribe to start the channel, unsubscribe to stop it.
args	List<Object>	The channels to act on. Each entry names one.
args[].instType	String	Always UTA, for the unified trading account.
args[].topic	String	Always fill.

What arrives

fill: A message with the event subscribe and the same arg confirms the subscription, with a connId for the connection. On an error the event is error, with a code and a msg. Data then arrives as below.

The vendor's page does not say which of these fields are required or always present.

Name	Type	Description
arg	Object	The channel the data belongs to: the instType, the topic and, on a public channel, the symbol that were subscribed to.
action	String	snapshot, for full data.
data	List<Object>	The fills.
data[].category	String	The product type: spot, margin, usdt-futures, coin-futures or usdc-futures.
data[].orderId	String	The id of the order.
data[].clientOid	String	The client's own id for the order.
data[].execId	String	The id of the fill.
data[].execLinkId	String	An id that links related executions.
data[].symbol	String	The symbol.
data[].orderType	String	limit or market.
data[].side	String	buy or sell.
data[].holdSide	String	The direction of the position: long or short.
data[].tradeSide	String	open or close.
data[].execPrice	String	The fill price.
data[].execQty	String	The quantity filled, in the base coin.
data[].execValue	String	The value filled, in the quote coin.
data[].execPnl	String	The profit and loss of the execution.
data[].tradeScope	String	taker or maker.
data[].feeDetail	String	The fees. Each entry holds a feeCoin and a fee.
data[].execTime	String	When the matching engine made the fill, as Unix time in milliseconds.
data[].updatedTime	String	When the fill was updated, as Unix time in milliseconds.
data[].isRPI	String	yes where it is an RPI fill, no where it is not.

Sample

Written by this site from the fields recorded on this page. It has not been run against a terminal, a server or an account, and the values in it are placeholders. No credential is typed into it: where a field holds one, the placeholder says where it comes from. Nothing is entered on this site.

{
  "op": "subscribe",
  "args": [
    {
      "instType": "UTA",
      "topic": "fill"
    }
  ]
}

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 12 Oct 2026
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 12 Oct 2026
Concurrent WebSocket connections	100	Per IP address	bitget.comchecked 12 Oct 2026
WebSocket messages a second	10	Per WebSocket connection, counting ping, login, subscribe and unsubscribe messages	bitget.comchecked 12 Oct 2026
WebSocket subscription requests an hour	240	Per WebSocket connection	bitget.comchecked 12 Oct 2026
Concurrent WebSocket channel subscriptions	1,000	Per WebSocket connection	bitget.comchecked 12 Oct 2026