Binance Open Platform API Update Log

The Binance Open Platform regularly introduces improvements, new features, and critical updates to enhance performance, security, and functionality across its REST, WebSocket, and FIX APIs. This comprehensive update log details recent and upcoming changes—spanning API behavior adjustments, new parameters, deprecations, and structural upgrades—essential for developers building trading systems, bots, or data analysis tools.

Whether you're integrating real-time market data streams, managing user account events, or optimizing order execution logic, staying current with these changes ensures seamless operation and avoids unexpected disruptions.

Recent Updates (2025)

July 3, 2025: WebSocket Account Interface Upgrade

• Starting July 8, 2025, at 07:00 UTC, the WebSocket Account Interface will undergo a system upgrade.
• During this period, existing and new connections may disconnect for up to 24 hours.
• The actual upgrade process is expected to take no more than 2 hours. Users are advised to plan accordingly.

👉 Discover how real-time trading platforms handle system upgrades and maintain reliability.

June 4, 2025: SBE 2.0 Schema Deprecation

• The SBE 2.0 schema will be disabled on June 12, 2025, six months after deprecation as per the SBE policy.
• Developers must migrate to newer schema versions before this date to avoid service interruption.
• The production SBE lifecycle JSON has been updated to reflect this change.

May 28, 2025: API Timeout and Error Documentation

• Detailed timeout values and error handling information have now been documented for all major API types:

  • FIX API
  • REST API
  • WebSocket API

This improves transparency and helps developers design more resilient retry and fallback mechanisms.

May 22, 2025: Enhanced recvWindow Timing Security

Effective June 6, 2025, at 07:00 UTC, an additional timing security check will be enforced across FIX, REST, and WebSocket APIs:

• Existing checks remain: Requests rejected if:

  • timestamp > serverTime + 1 second
  • |timestamp - serverTime| > recvWindow

• New check added: If |timestamp - serverTime| > recvWindow before reaching the matching engine, the request is rejected—and now counts toward:

  • Message rate limits (FIX)
  • IP rate limits (REST/WebSocket)
  • Unfilled order count (all APIs’ order endpoints)

This strengthens protection against replay attacks but requires tighter client-server clock synchronization.

Documentation updates:

• REST API Timing Security
• WebSocket API Request Security
• FIX API Timing Security

Additionally, a bug in the FIX Market Data InstrumentList message has been fixed where NoRelatedSym(146) could return incorrect values.

April 29, 2025: Broader API Key Support for WebSocket Streams

Features previously restricted to Ed25519 API keys will soon support HMAC and RSA keys as well. For example:

• Subscribing to account data streams via WebSocket without requiring Ed25519.

However, Ed25519 is still recommended due to superior security and performance in spot trading environments.

More details will be published soon.

April 25, 2025: Increased Request Weight for Order Amendments

The request weight for the following endpoints increases from 1 to 4:

• REST: PUT /api/v3/order/amend/keepPriority
• WebSocket: order.amend.keepPriority

Documentation has been updated to reflect this change.

Also clarified: In FIX API, SEQNUM is a 32-bit unsigned integer that wraps back to zero after reaching its maximum value—a behavior consistent since launch.

April 21, 2025: Order Amend Keep Priority & STP DECREMENT Launch

Key features go live globally on May 7, 2025, at 07:00 UTC:

• Order Amend Keep Priority: Modify orders while preserving their queue position.
• Self-Trade Prevention (STP) mode DECREMENT: Reduces available quantity for both taker and maker sides when a self-trade is prevented.

Starting April 24, 2025, the amendAllowed field becomes visible in exchange info responses—though functionality remains inactive until full rollout.

Both features are already active on the SPOT Testnet.

April 8, 2025: New Error Codes and Query Clarifications

Gradual rollout (up to one week):

• New error code -2039: Returned when querying an order with both orderId and origClientOrderId, but no matching order exists.

  • Affected endpoints:

    • REST: GET /api/v3/order
    • WebSocket: order.status
• Error code -1034 message updated for FIX connection rate limit exceeded scenarios.

April 7, 2025: Major Structural Updates

General Changes

Gradual rollout ongoing:

• FIX Market Data session connection limit increased from 5 to 100 (previously undocumented).
• New error code -2038 for failed "amend keep priority" requests.
• Unfilled order count under intervalNum:DAY now caps increments for intervalNum:SECOND.
• myTrades weight drops from 20 to 5 when orderId is provided.
• Query/delete requests now reject with -1102 instead of -1128 if both orderId and origClientOrderId are missing.

FIX API Updates

Effective April 21:

• Enforced validation of EncryptMethod(98) = 0 during Logon.
• Per-account limit of 10 concurrent TCP connections for order entry sessions.

• Connection rate limiting introduced:

  • Order Entry & Drop Copy: 15 attempts / 30 seconds
  • Market Data: 300 attempts / 300 seconds
• News messages now include countdown alerts during maintenance; sent every 10 seconds for 10 minutes, then session logout.
• Support added for using orderId and clientOrderId in cancellation requests.
• QuickFix schema updated to support Order Amend Keep Priority and STP DECREMENT.

User Data Streams Deprecation Notice

Important: The legacy method of accessing user data via listenKey at wss://stream.binance.com:9443 will be deprecated.

✅ Recommended alternative: Subscribe directly via the WebSocket API account stream, which offers lower latency and requires Ed25519 keys.

Future updates will:

• Remove basic WebSocket account URL references.

• Delete legacy endpoints:

  • POST /api/v3/userDataStream
  • PUT /api/v3/userDataStream
  • DELETE /api/v3/userDataStream
  • And corresponding WebSocket methods (userDataStream.start, etc.)

Payload documentation remains available for reference.

Upcoming Changes (April 24, 2025)

New field amendAllowed appears in:

• REST: GET /api/v3/exchangeInfo
• WebSocket: exchangeInfo

SBE schema version 3.0 (spot_3_0.xml) released:

• Supports Order Amend Keep Priority and STP DECREMENT.
• Replaces deprecated schema 2.1, which will be phased out in six months.

• Breaking changes include:

  • Removal of enum values: AUCTION_MATCH, PRE_TRADING, POST_TRADING
  • New required fields: usedSor, orderCapacity, workingFloor, etc.
  • Optional field orderCreationTime in ExecutionReportEvent.

Older schemas (<3.0) cannot represent responses involving STP DECREMENT or amend keep priority—will return errors.

👉 Explore next-generation trading APIs with advanced order types and low-latency execution.

Historical Updates (2024–2018)

March–December 2024

SBE Market Data Launch (March 18)

Low-latency SBE streams launched:

• Trade-by-trade
• Top-of-book
• Incremental depth (every 100ms)

Microsecond Timestamp Support (December)

Opt-in microsecond precision added via:

• Header: X-MBX-TIME-UNIT
• URL param: timeUnit=MICROSECOND

Applies to REST, WebSocket API, and user streams.

OCO Enhancements (December)

Support added for:

• TAKE_PROFIT + STOP_LOSS
• TAKE_PROFIT_LIMIT + STOP_LOSS_LIMIT

Legacy error -1167 deprecated.

Permission Sets Overhaul (April)

Permissions moved from flat array permissions to nested arrays permissionSets, enabling complex access rules like [["SPOT","MARGIN"],["TRD_GRP_004"]].

New field otoAllowed indicates support for One-Triggers-the-Other orders.

SBE Production Rollout (February)

SBE deployed to live REST and WebSocket APIs—improving speed and efficiency.

Prior Years Highlights

Self-Trade Prevention (STP) – January 2023

Launched with modes:

• EXPIRE_TAKER
• EXPIRE_BOTH
• EXPIRE_MAKER
• DECREMENT

New endpoint: /api/v3/myPreventedMatches

Trailing Stop Orders – April 2022

Introduced via trailingDelta parameter (in bips), supported on STOP_LOSS and TAKE_PROFIT order types.

Cancel & Replace Orders – June 2022

Added atomic cancel-and-place functionality via /order/cancelReplace.

Multiple API Clusters – Late 2022–Early 2023

Introduced redundant endpoints (api1–api4.binance.com) and GCP-based fallback (api-gcp.binance.com) for improved reliability.

Core Keywords

Binance API updates, WebSocket API changes, REST API enhancements, FIX protocol updates, SBE schema migration, order amendment keep priority, self-trade prevention (STP), real-time market data integration

Frequently Asked Questions

Q: What happens if I don’t migrate from SBE 2.0 before deprecation?
A: After deprecation, your application will receive errors when attempting to use unsupported message formats. Migrate to SBE 3.0 to ensure compatibility with new features like STP DECREMENT and Order Amend Keep Priority.

Q: Why was the request weight increased for certain endpoints?
A: Higher weights reflect increased server-side processing costs. This helps maintain platform stability by discouraging excessive polling or high-frequency usage without proper optimization.

Q: How do I prepare for the listenKey deprecation?
A: Transition to subscribing directly through the WebSocket API using Ed25519 keys. This method provides lower latency and aligns with modern authentication standards.

Q: What does STP mode DECREMENT do?
A: When a self-trade is detected, it reduces the available quantity of both conflicting orders equally—preventing either side from fully executing while preserving partial fill eligibility.

Q: Can I still use HMAC keys after April 30?
A: Yes. While Ed25519 is recommended for performance and security, HMAC and RSA keys will continue to work for most functions—including newly expanded WebSocket access.

Q: How can I test upcoming changes safely?
A: Use the Binance SPOT Testnet environment where all new features are deployed ahead of mainnet launch.