Technologie & IA
OKX moves testing of its new binary feeds to November 13
Documentation updated on November 12, 2026 schedules the demo launch of SBE order entry and private feeds for the following day. Production remains planned for early December.

A revised timetable for testing
On November 12, 2026, OKX updated the timetable for two new WebSocket services that use Simple Binary Encoding, or SBE. The exchange now expects them to open in its demo environment on November 13. The previous version of the documentation listed November 12. The production launch remains planned for early December, with no specific day. These are scheduled dates. The update does not confirm a production launch.
The first service receives requests to place, amend and cancel orders. It covers single orders and batches, with a stated maximum of twenty orders per batch. The second service sends private updates. The two services have separate WebSocket paths and use different hosts for demo and production. OKX says its existing REST and JSON WebSocket APIs remain available.
Two XML schemas define the messages
SBE encodes data in binary frames with a layout defined by a schema. Control messages still use JSON in text frames. OKX says the new feeds authenticate during the WebSocket upgrade request, using an API key and signature in the headers. The two services share a limit of 500 connection requests per five minutes per IP address.
OKX also changed the XML schemas before launch. The order entry schema moves to semantic version 2.0.0. Some time fields now use the suffix Us for microseconds, with the units unchanged. Order placement responses drop one instrument identifier and move the fixed fields that follow it. Batch responses retain the request order and provide error messages associated with individual orders. These changes explain why the exchange asks developers to regenerate their encoders and decoders using the updated schemas.
Private feeds start without a snapshot
The orders channel is meant to send a message when an order is created or changes state. The fills channel is meant to report order book executions and is available to VIP4 users and above. According to the documentation, neither channel sends an initial snapshot on subscription. Subscription messages and responses remain in JSON, while channel data uses the binary format.
For order entry, OKX says it will support CASH and CROSS modes. It directs clients that use another mode to the JSON WebSocket interface. The demo environment is meant to let clients test message decoding and response handling before production opens. The November 12 update changes the testing date and provides the schemas for that stage.
