BitMEX Binary WebSocket Trading API adds request correlation fields

Published: 2026-06-16 02:07:53 |

BitMEX announced an update to its Binary WebSocket Trading API. From 17 June 2026 (06:00–09:00 UTC), the SBE schema version will move from v5 to v6, affecting the binary WebSocket Trading API error handling and trade execution messages. In the Binary WebSocket Trading API: - ErrorMessage (template ID 106) will gain new optional fields: clOrdID and orderID. When the gateway rejects a request, these fields echo the client order ID and/or server order ID from the originating request, so clients can correlate errors to specific orders. - ErrorMessage will also add requestType, carrying the SBE template ID of the originating request (e.g., 100 for NewClientOrder, 101 for AmendClientOrder). This follows the same correlation convention already used on RequestStatus (template ID 110). - TradeExecution (template ID 105) will gain optional tradePool, identifying the counterparty pool for a trade fill. BitMEX frames this as additive only: no existing fields are removed or changed. Clients decoding with older schema versions (v5 or earlier) will receive null sentinels and should treat these fields as absent. For traders and API integrators running high-frequency order flow, the update reduces reliance on external state to map gateway errors back to orders, improving automation reliability around BitMEX’s derivatives and execution pipeline.

Neutral

This is a technical, additive API change to BitMEX’s Binary WebSocket Trading API that improves how errors and executions can be correlated back to specific client orders. It does not change trading fees, leverage limits, or market structure, so direct price impact should be limited. In the short term, traders who rely on automated order management may need to update their message decoders to SBE v6 to use the new clOrdID/orderID/requestType/tradePool fields. That can slightly affect integration workflows, but it’s not a market-wide catalyst. In the long term, better request correlation typically reduces operational risk in high-frequency systems. Fewer ambiguous gateway errors can lead to more stable execution and monitoring, which may modestly improve execution quality rather than shifting market fundamentals. Historically, similar incremental API observability upgrades tend to be net neutral for spot/perp prices, while benefiting bots and institutional tooling.