Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Binance reminds API clients of 9 November SBE 3:3 retirement as market-data formats change

The spot exchange’s 30 October changelog identifies an upcoming schema sunset; integrators must distinguish a data-format migration from an exchange-wide trading shutdown.

Binance’s spot API changelog updated on 30 October 2026 warns that Simple Binary Encoding schema version 3:3 is scheduled for retirement on 9 November. The notice says the format had been deprecated six months earlier. This is an integration deadline for software consuming the affected binary market-data or order-interface messages, not an announcement that spot trading or Binance’s entire REST and WebSocket API will cease on that date.[1]

SBE is a machine-readable messaging format used in latency-sensitive trading infrastructure. A schema version determines how fields are represented and interpreted; an application compiled against an obsolete schema can fail to decode a newer payload correctly even when the underlying prices and orders are valid. The immediate operating risk is therefore compatibility across clients, feed handlers, serializers and monitoring tools.[1]

The announced technical change

At a glance01

What the changelog establishes

What the changelog establishes
ItemStatus
Affected schemaSBE 3:3
Notice published30 October 2026
Scheduled retirement9 November 2026
Prior statusDeprecated approximately six months earlier
Broader exchange operationsNo general shutdown announced in this entry

A broker, execution vendor or proprietary trading firm consuming a Binance spot feed should identify which schema its running services negotiate or expect, then test against a supported replacement and monitor the parse error rate, field mappings and order-session recovery logic. That is a practical implication of an announced format retirement, not a claim that Binance has published a mandatory migration checklist for every possible client architecture.[1]

The changelog also records a documentation update for an earlier FIX API field. A documentation change and a live protocol change are not necessarily the same event; production operators should compare the official implementation and schema files before adjusting downstream logic. The posted lifecycle date is specific to SBE 3:3, so it must not be confused with the earlier retirement date of SBE 3:2 in September.[1]

The relevance to broker infrastructure is narrow but concrete. Market-data gateways and order-routing systems can be technically operational while silently losing parts of their feed when a binary message version changes. The notice provides a dated test and cutover point. It contains no exchange-wide volume estimate, outage forecast or completed customer migration count.[1]

Follow the evidence

Sources & further reading

  1. CHANGELOG for Binance Spot REST and WebSocket API Binance Developers · 30 Oct 2026 · Accessed 31 Oct 2026
  2. Binance Spot API documentation Binance Developers · Accessed 31 Oct 2026

Report an error or submit an update