BitMEX Binary WebSocket Trading API don add request correlation fields
BitMEX don announce update for im Binary WebSocket Trading API. From 17 June 2026 (06:00–09:00 UTC), dem go move SBE schema version from v5 to v6, wey go affect how binary WebSocket Trading API dey handle errors and trade execution messages.
For the Binary WebSocket Trading API:
- ErrorMessage (template ID 106) go get new optional fields: clOrdID and orderID. When gateway reject request, these fields go echo the client order ID and/or server order ID from the original request, so clients fit match errors to specific orders.
- ErrorMessage go also add requestType, wey carry the SBE template ID of the original request (e.g., 100 for NewClientOrder, 101 for AmendClientOrder). This one follow the same correlation convention wey dey used already for RequestStatus (template ID 110).
- TradeExecution (template ID 105) go get optional tradePool, wey identify the counterparty pool for a trade fill.
BitMEX talk say na only add-on: dem no remove or change any existing fields. Clients wey decode with older schema versions (v5 or earlier) go receive null sentinels and suppose treat these fields as absent.
For traders and API integrators wey dey run high-frequency order flow, the update go reduce reliance on external state to map gateway errors back to orders, and e go improve automation reliability around BitMEX derivatives and execution pipeline.
Neutral
Dis na technical, additive API change for BitMEX Binary WebSocket Trading API wey improve how errors and executions fit dey correlated back to specific client orders. E no change trading fees, leverage limits, or market structure, so direct price impact suppose dey limited.
For short term, traders wey dey rely on automated order management fit need update their message decoders to SBE v6 to use the new clOrdID/orderID/requestType/tradePool fields. That fit small affect integration workflows, but e no be market-wide catalyst.
For long term, better request correlation usually reduce operational risk for high-frequency systems. Less ambiguous gateway errors fit lead to more stable execution and monitoring, wey fit small improve execution quality instead make e change market fundamentals. Historically, similar incremental API observability upgrades dey usually net neutral for spot/perp prices, while e dey benefit bots and institutional tooling.