Binance API changes that can break a third-party tool connection
Dated Binance Spot API changes, from new symbol statuses and WebSocket disconnect notices to request-weight rules and schema retirements, and what each one means for a third-party tool connection.
SBE schema 3:2 retired on 25 September 2026
The changelog reminded users that SBE schema 3:2 for the REST and WebSocket APIs, and FIX SBE 1:0, would be retired on 2026-09-25. Most dashboards read JSON and are unaffected; a tool that requests SBE responses on the old schema needs a release that uses a current one.
Key creation and IP restrictions
Review the official API creation guide. Default security controls restrict non-reading access on system-generated HMAC keys without IP restrictions. Do not disable controls to troubleshoot.
Permissions and error codes
Check the official permission categories and the meanings of -2015, -1021, -1022 and HTTP 429. Read the tool documentation alongside the platform documentation.
New symbol status CANCEL_ONLY
From 2026-07-07, exchange information can report a symbol as CANCEL_ONLY. A tool that only knows TRADING, BREAK and similar older values may show an error or hide the pair. If one market suddenly looks broken in a tool while others work, check the symbol status first.
WebSocket Streams upgrade on 9 July 2026
Binance announced an infrastructure upgrade for WebSocket Streams starting 2026-07-09 07:00 UTC, lasting up to about an hour, during which connections could drop. A tool that does not reconnect on its own will show stale prices or balances until it is restarted.
serverShutdown event before a disconnect
From 2026-05-08, the WebSocket API and WebSocket Streams send a serverShutdown event before a server closes the connection; the client should open a new connection when it arrives. A documentation update on 2026-06-09 dropped the promise of a fixed lead time, so a tool should reconnect when the event arrives rather than count down a timer.
Request weight for successful order requests
From 2026-04-02, the RAW_REQUESTS limit rose to 300,000 per 5 minutes, and successful order placement and cancellation requests are charged zero request weight. Failed requests still count. Per the changelog, an IP that only sends these requests successfully will not hit the REQUEST_WEIGHT limit, so when a tool gets a 429, look first at its data reads: history syncs and repeated refreshes.
When this page is updated
We update this page when Binance publishes a relevant API change or a connection problem can be reproduced. When nothing changes, we recheck the official sources once a month.
Sources & verification
Entries dated March to September 2026 use the announcement dates in Binance’s Spot API changelog, read on 15 October 2026. Effective dates are given inside each entry.