Skip to main content
Query or subscribe to executed order history with optional filtering by order type (limit, market, or both). Each record includes execution details, fees, and status. Update interval: real-time.
Connect to wss://wss.whitebit.com/ws — see WebSocket Overview for protocol details and keepalive requirements.

Rate limits

Query executed orders (one-time)

Fetch historical executed orders for a market without subscribing. Request Response
The private stream returns executed orders, including orders using Retail Price Improvement (RPI) mode.

Subscribe to executed orders

ordersExecuted_update events do not include the source field. To identify Auto-Deleveraging (ADL) and liquidation orders in updates, match the client_order_id prefix: adl_<order_id>_! or liquidation_<order_id>_!. See Identifying liquidation and ADL fills.
Orders with type 14 are system-generated balance normalization orders, not orders the account placed, and carry an empty client_order_id. Normalization orders run on <ASSET>_USDT markets, so the ordersExecuted_subscribe market list must include those markets.
Execution events during a disconnection are not replayed. After reconnecting, use ordersExecuted_request to query recent executed orders, or call the REST Executed Order History endpoint to backfill missed records. See Reconnection and state recovery.

Update frequency

Updates are pushed in real time when an order is fully executed or canceled.

Error codes

Executed order object

Used in these guides

  • Copy Trading — mirror a lead trader’s orders into followers’ own accounts via OAuth-issued keys.