Upcoming and recent changes to the market data feeds and APIs we handle, collected hourly from each exchange's changelog, notices and status page, and summarized automatically. Each entry links to its source; check it before acting. RSS / Atom feed
New endpoints: POST /flight_disruption_markets creates the market for a flight, with a cover (including delayed) and, for delayed, a delay_basis (departure or arrival) and delay_minutes. It returns 409 flight_disruption_market_unavailable if the request cannot be offered, and 429 flight_disruption_market_limit_exceeded when the creation limit is reached (not request-rate limiting). GET /flight_disruption_markets/availability lists available covers and delays, scheduling windows and departure countries. GET /flight_disruption_markets/flights looks up flights by number and date. No action is needed for our order book handling.
Our handler: These are market-creation and lookup endpoints for KXRFQFLIGHT markets, not the orderbook_delta channel or the open-markets list for the series we track.
Our execution provider for US Futures has scheduled maintenance starting at 00:30 UTC on 21 November, planned for up to 1.5 hours. This affects US Futures only (CME Group 24/7 futures products and Bitnomial perpetual futures). During the window, clients will not be able to place, modify, cancel, or close orders or positions, including via API. Market data may also be affected. We recommend closing any positions and canceling any working orders you do not wish to carry into the maintenance window. Linear multi-collateral derivatives for non-US clients and all other products are not affected.
Our handler: Affects: Market Data, Bitnomial Exchange (BTNL), Order Placement
Once an account hits its limit, a request that would create a new market returns the existing error code flight_disruption_market_limit_exceeded, and the message says it is the account's limit. Requests that return an existing market (created: false) do not count toward the limit and are still answered at the limit. No error codes are added or changed. This is an on-request market creation endpoint; a market data client that only reads order books and the public market list needs to do nothing.
Our handler: POST /flight_disruption_markets is an account-level market creation endpoint, not the orderbook_delta channel or the public market list we use.
The page text is truncated and does not name the endpoint or field. Futures is now supported in addition to spot. Our handler only uses spot order book and trade data, so check that none of the REST or WebSocket calls it uses return this field.
Our handler: The endpoint and field are not named in the text, so it cannot be ruled out that it touches market data symbol info.
These are account-level functions for FUNDING or SPOT accounts covering eligible currencies, conversion requests, order lookup and paginated history. They need no change for public market data consumers.
Our handler: These are account and conversion endpoints, not the public level2 or match channels or the REST order book snapshot.
The text gives no specifics on what changed in the rate limit pool. It appears to relate to account management rather than public data. Review rate limit documentation if our REST snapshot calls are throttled.
Our handler: Rate limits could affect REST snapshot requests to level2_100, but the text gives no details.
No further detail is given. UTA is an account and trading product. Our handler uses the classic spot WebSocket and REST endpoints and needs no change.
Our handler: UTA API V2 is a separate account and trading API, not the spot level2, match or snapshot endpoints we use.
No date is given for the deprecation. Clients that match on error codes 111202 or 111209 should also handle 111235. This appears tied to the UTA API, so it is likely irrelevant to our public feed, but check any error handling keyed on these codes.
Our handler: The text does not say which endpoints return these codes, and our REST snapshot error handling could be affected if it keys on them.
The fragment says an unnamed endpoint takes up to 100 comma-separated market tickers in a query parameter, and a single ticker still works. Existing single-ticker requests keep working, so no migration is needed. Check the full changelog entry to see which endpoint this is and whether it is one our handler calls, such as the public markets list.
Our handler: The endpoint is not named, so it may be the public markets list our handler polls or it may be a different endpoint.
A new endpoint for querying the Bybit card list was added. It relates to card features, not public order book or trade data. No action is needed for market data handlers.
Our handler: Card list endpoint is an account-related feature outside the public spot orderbook channel and REST orderbook snapshot.
A new endpoint for querying the Bybit card limit was added. It relates to card features, not public order book or trade data. No action is needed for market data handlers.
Our handler: Card limit endpoint is an account-related feature outside the public spot orderbook.200 channel and /v5/market/orderbook snapshot.
RFQs on request-created markets, combos whose legs are all such markets, and RFQ batches of such combos always obscure the creator's public communications ID. Other users get the shared placeholder in RFQ responses, broadcasts and quotes until execution; the creator still sees their own ID. RFQs on other markets are unchanged. This concerns RFQ and quote communications, not the orderbook_delta channel or the market list, so no action is needed for a public order book handler.
Our handler: RFQ and quote communications are outside the orderbook_delta channel and the public market list that our handler uses.
The notice concerns execution reports and invoices, which are trading and post-trade items. No XDP market data message or field is mentioned. No action is needed for a market data handler. No effective date is given in the text.
Our handler: It concerns execution reports and invoices (trading and post-trade), not the XDP public market data feeds.
The notice is titled as a trading resumption in GNS. A resumption after a halt would normally be shown in Security Status messages on the feed. The text gives no times and no other details. No client action is required beyond handling the status change as usual.
Our handler: A trading resumption in a symbol would be reflected in Security Status messages on the XDP feed, though the text gives no detail.
The page text gives only a headline and the areas covered, with no details on what changed, no effective date and no version number. Our handler uses NYSE XDP equities feeds, not options feeds, so no action is evident. Review the full specification only if options data is ever consumed.
Our handler: The update concerns NYSE American Options and NYSE Arca Options, while our handler consumes XDP Integrated, Imbalances and Trades equities feeds.
Affected raw channels include book raw subscriptions (merged changes with an unbroken prev_change_id/change_id chain), quote.{instrument_name} (latest value only), trades.{kind}.{currency}.raw (trades batched together) and raw order channels (only the last order state in the window). A quiet channel still sends the next change immediately. Merged notifications could already occur under very high load. Clients that treat each notification as a complete update need no change, and should not rely on seeing every intermediate state. Our handler uses the 100ms book channel, not raw, so impact is likely limited.
Our handler: The change targets raw subscriptions, while our handler uses book.<instrument>.100ms, which is not listed as affected, though raw book change_id chaining is mentioned.
Swaps wallets are created by Kalshi and are separate from the primary account and numbered subaccounts. Clients that switch exhaustively on subaccount_type should accept the new value. This concerns balance, position and risk rows, which are account data; our handler only consumes public order book data, so no action is needed.
Our handler: The subaccount_type field appears on margin balance, position and risk rows (account data), not on the public orderbook_delta channel or market list.
Per the fragment, once a market's close_time (or the show's start) is 24 hours away or less, the request returns an error code with a reason instead of the market being returned. The market stays open until close_time, positions are unaffected, the market endpoint still returns it, and settlement is unchanged. The text is incomplete, so the exact endpoint is unclear. Market-list consumers should verify that markets near close still appear as expected.
Our handler: The fragment says the market list endpoint still returns such markets, but the wording is incomplete and may relate to order creation only.
The change applies to order placement endpoints only. Requests that omit the field fail with missing_parameters, and values other than the accepted one are rejected. On Margin the order was previously sent as an ask. Read-only market data clients do not need to act.
Our handler: Create, Amend and Batch Create Order endpoints are trading endpoints, not the public order book data we consume.
The fragments describe a stricter lead time: a new market is held to a 7-day window instead of 24 hours, and a request returns something when the date, whichever is earlier, is 7 days away or less. The source does not say which endpoint or request is involved, and it gives no effective date. Market-data clients should check the full changelog entry. Our handler only reads the public market list and orderbook_delta, so the impact is probably limited to when new markets appear.
Our handler: This appears to concern market creation timing, which could change when new markets show up in the REST market list, but the text is incomplete and does not name an endpoint.
Only the headline was available, with no effective date or technical detail. It concerns options quoting differentials, not the equities XDP feeds our handler consumes. No client action is indicated.
Our handler: The notice is about NYSE Options quoting differentials, not the NYSE equities XDP Integrated, Imbalances or Trades feeds we use.
Spot transfers need an API key with withdrawal permission and cost 100 rate-limit units. Futures-to-Futures transfers cost 10 units and now return specific refusal reasons instead of always insufficientFunds. This is an account and funds change with no effect on public market data.
Our handler: Concerns Derivatives account transfer endpoints (/transfer, /transfer/assets), not the Spot WS v2 book or trade channels.
Use POST /transfer with toAccount=spot instead of POST /withdrawal. Transfers made with POST /transfer appear in the account log rather than in GET /transfers. These are account and funds endpoints only.
Our handler: Affects Derivatives account endpoints /withdrawal and /transfers, which our public Spot market data handler does not use.
The new error is makerProtectionOrderLimitExceeded (REST v3), MAKER_PROTECTION_ORDER_LIMIT_EXCEEDED (REST v4 and FIX). It was previously reported as tooManyOrders. This is a trading-only change.
Our handler: Applies to Derivatives order-entry errors and the cancelallorders endpoint, not public market data.
Markets created after the WebSocket server started used to get their UUID and creation clock in the snapshot. They now behave like markets that predate the server. Key these markets by market_ticker, not market_id. The first orderbook_delta for the market carries its market_id, so the handler should fill it in from there.
Our handler: The Predictions orderbook_delta channel sends orderbook_snapshot messages whose market_id and clock can now be empty or 0.
Cursors carrying such text are handled as each endpoint already handles an undecodable cursor. Most endpoints return 400, while some, including GET /markets, ignore the cursor and return the first page. Valid requests and API-issued cursors are unaffected, so no client change is needed.
Our handler: Only malformed requests to REST endpoints such as /markets change behaviour; valid requests are unaffected.
The endpoints are POST /concert_cancellation_markets, GET /concert_cancellation_markets/availability, GET /concert_cancellation_markets/concerts and GET /concert_cancellation_markets/concerts/search. Trading goes through RFQs. The markets are not live yet. No client action is needed.
Our handler: New RFQ concert market endpoints are outside the BTC, ETH, SOL, XRP, metals and index series we consume.
429 responses carry them too, but not Retry-After. Publicly cacheable responses, which include most market data, carry none of them. Clients may read the headers for throttling but nothing breaks if they ignore them.
Our handler: Applies to REST responses, but the public market list we poll is mostly cacheable and carries no headers.
Some markets in events with several date strikes reported the last strike's date, which could fall after their own latest expiration. Markets already at or before the latest expiration are unchanged. Check any logic that reads expected_expiration_time from the market list.
Our handler: The /markets list we use returns market objects whose expected_expiration_time value changes.
latest_expiration_time has always carried the same value. Order expiration_time is unrelated and unchanged. Update any parser of the /markets response that reads market expiration_time to read latest_expiration_time.
Our handler: The GET /markets?status=open&series_ticker= market list returns market objects that lose the expiration_time field.
Orders outside the band are rejected with invalid price. When the band takes effect or moves, resting orders outside it are canceled. Margin user_orders and orderbook delta messages report last_update_reason SettlementBoundsCancel, and FIX ExecutionReports carry SETTLEMENT_BOUNDS_CANCEL. Book handlers may see level removals with this new reason value.
Our handler: Margin orderbook_delta messages can now report last_update_reason SettlementBoundsCancel when resting orders are canceled.
Each program now also carries series_ticker and event_ticker. The endpoint needs no authentication. No client action is needed.
Our handler: Incentive endpoints are not part of the order book or market list we consume.
We will be undergoing scheduled maintenance during this time.
Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API
Kraken Prime will be undergoing maintenance as we upgrade our systems on Thursday, Nov 19 at 21:00 UTC. Existing connections will be disconnected and reconnection is possible after the 15 minute maintenance window. We kindly advise our clients to plan ahead accordingly and make necessary account adjustments prior to the start of the maintenance.
Our handler: Affects: FIX, REST, WebSocket
The request takes an optional end_date. If omitted or equal to date, behaviour is unchanged. If set to the day after date, the window runs from start_hour on date to end_hour on end_date, at most 24 hours, so end_hour must not be after start_hour; any other end_date or a longer window returns 400. Where max_window_days is 1, a new market whose window is stored across two local dates returns 409. Existing markets are returned either way. Tickers keep their shape: the UTC start plus length in hours (e.g. ...-26NOV2404Z-4H-...). Our handler consumes only the orderbook_delta channel and the market list for the listed crypto, metals and index series, so no action is needed.
Our handler: This concerns the on-request weather market creation endpoint, which our handler does not use; it follows the tracked orderbook_delta channel and the market list for crypto, metals and index series only.
We're pleased to announce that the Unified WebSocket API is now available for Derivatives. It gives clients a single WebSocket interface for both spot and derivatives. Spot is expected early next year. Along with market data and accounting, trading is now also available for derivatives via WebSocket. The public endpoint is uws.kraken.com/v2/public, while the private one is uws.kraken.com/v2/private. SDKs to integrate with Unified WebSocket are now available. The Derivatives WebSocket APIs are now deprecated and will be decommissioned on 1st March 2027. Documentation: https://docs.kraken.com/exchange/api-reference/unified-websocket SDKs: https://docs.kraken.com/home/sdks/index If you have questions or run into issues, please contact Kraken Support.
Our handler: Affects: Websocket API, Unified WebSocket
The notice only states a trading resumption for FMBM on NYSE American. No protocol or format change is described. Handlers may see Security Status messages reflecting the halt-to-trading transition for this symbol; no client action is required.
Our handler: A trading resumption would appear as a Security Status update for FMBM on the NYSE American XDP feed.
The notice only states a trading resumption for 11 ProShares ETFs on NYSE Arca Equities. No protocol or format change is described. Handlers may see Security Status messages reflecting the resumption for these symbols; no client action is required.
Our handler: A trading resumption would appear as Security Status updates for the affected symbols on the NYSE Arca XDP feed.
The new limit is shared across the listed ticker and order book methods. It comes on top of the default non-matching engine limit of 20 requests per second (burst 100), so each call counts against both. The page text does not list the methods (the list appears to be missing from the text), but get_order_book is likely among them. Clients should reduce polling, such as REST snapshot requests, and handle error 10028 with backoff. Deribit recommends subscribing to WebSocket channels instead of polling.
Our handler: Our REST snapshot uses public/get_order_book, which is likely among the order book methods covered by the new 5 req/s limit, though the source text does not name the methods.
For markets created from now on, title and rules_primary give the window in the location's zone regardless of the zone in the request. Where max_window_days is 1, a window crossing midnight at the location is refused with 409. A window crossing midnight and longer than 24 hours there returns 400. A location whose time zone cannot be determined returns 409. This concerns market creation, not the order book feed; any parsing of title or rules_primary text for weather markets should expect the new wording.
Our handler: It concerns weather point market creation and title/rules_primary text, while our handler uses orderbook_delta and the market list for crypto, metals and index contracts.
This is an optional setting on the RFQ session and needs no action. It concerns account execution reports, not public market data.
Our handler: KalshiRFQ session execution reports are account and trading functionality, not the public orderbook_delta channel or market list we consume.
A new bond listing was added on NYSE Bonds. No protocol, message format or feed changes are described. No client action is required.
Our handler: The notice covers a bond listing on NYSE Bonds, which is not part of the XDP equity feeds we consume.
Three new bond listings were added on NYSE Bonds. No protocol, message format or feed changes are described. No client action is required.
Our handler: The notice covers bond listings on NYSE Bonds, which is not part of the XDP equity feeds we consume.
New endpoints: GET Get locked Travel Rule deposits and POST Unlock Travel Rule deposit. Error codes 58385-58389 were added to the funding error code list. These are account and funding features; no change to public market data, books or trades channels. No action required for a market data client.
Our handler: The change covers account/funding deposit endpoints and error codes, not the public books or trades channels or the market books REST snapshot.
Two points in the same grid cell used to resolve to one market and now resolve to two. A rounded location exactly on a grid cell boundary is moved 0.001° north or east into one of the cells. Ticker format is unchanged, but the location segment (e.g. 40785N73965W) is the market's point and no longer always a cell center. Markets created before this change keep their location and stay reachable by requesting those coordinates. Our handler tracks only crypto, metals and index event contracts and perpetuals, so no action is needed.
Our handler: This concerns location-based weather markets, which are not among the BTC/ETH/SOL/XRP, gold/silver, S&P 500/Nasdaq-100 event series or perpetuals we consume via orderbook_delta and the markets list.
This is a regulatory halt resumption notice for a single symbol on NYSE American. No feed format, channel or field changes are stated. Handlers should process the associated Security Status message as normal; no client action is required.
Our handler: A halt resumption is reflected in the XDP Security Status message for ZOAR, but the notice itself changes no feed behavior.
This is a single-symbol trading halt notice. It is not an API or feed change. Market data clients may see a Security Status message for FMBM on the XDP feeds reflecting the halt. No client action is needed, and no date, resumption time or format change is given in the text.
Our handler: A regulatory halt in FMBM would show up as a Security Status message on the XDP feeds, but no protocol change is described.
New perpetual swap endpoint for chart-supported symbol lookup. No action is needed; our handler uses only spot WebSocket depth and trade channels.
Our handler: Swap REST endpoint; our handler uses only the spot WebSocket depth20 and trade channels.
New perpetual swap analytics endpoint. No action required for spot order book and trade handlers.
Our handler: Swap analytics REST endpoint, unrelated to spot depth20 or trade channels.
New perpetual swap analytics endpoint. No action required.
Our handler: Swap analytics REST endpoint, not used by our spot WebSocket handler.
New perpetual swap statistics endpoint. No action required.
Our handler: Swap REST endpoint, outside our spot depth and trade channels.
Documentation update with a revised time example. No action needed for spot WebSocket consumers.
Our handler: Swap mark-price candle REST documentation, not part of our spot channels.
Returns up to limit most recent records. This is a swap REST endpoint; our spot @trade WebSocket channel is not affected.
Our handler: Swap REST trades endpoint, not the spot @trade WebSocket channel.
The platform is back online and post-only has been removed.
Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API
The scheduled maintenance has been completed.
Our handler: Affects: Website, FIX, REST, WebSocket, Unified WebSocket, Embed
Gemini will perform scheduled Exchange maintenance beginning Tuesday, November 17th at 9:00pm ET. Some customers may experience brief connectivity interruptions through 11:59pm ET. Trading, deposit processing, contracts, and Prediction Markets will be unavailable from 12:00am to approximately 2:00am ET on Wednesday, November 18th. The website, mobile app, and balance checks will remain available throughout. Our team will share relevant updates here as the maintenance period progresses.
Our handler: Affects: Gemini ActiveTrader™, Exchange Trading Engine, REST API, FIX API, Websockets API, Recurring Orders, Gemini eOTC, Gemini Clearing, Wire Transfer Deposit and Withdrawals, Fiat Deposits and Withdrawals, Crypto Deposits and Withdrawals
The move happened on October 1, 2026. The new gateway uses JSON-RPC 2.0 over HTTP or WebSocket and the same CDP API key. Spot and US futures stay on the Advanced Trade API and are unaffected. A client consuming only spot level2 and market_trades data needs to do nothing. Only a client that used INTX perpetual data through Advanced Trade must migrate.
Our handler: Our handler uses only spot level2 and market_trades on advanced-trade-ws.coinbase.com, which the page says are unaffected.
This is an additive, authenticated institutional endpoint. Our handler uses public data with no auth, so no action is needed.
Our handler: It is an institutional account endpoint (/v5/ins/connection-limit) that our public handler does not use.
The changelog lists only the headline 'Open API 이용약관 개정 안내 (12/10 적용 예정)' (about 7 days before today). No details of the revised clauses are given. The terms page shown is the version applicable since 2024-10-30. Under the terms, users must review the notice and accept or reject the revision before the effective date. The year is inferred from the context of the current date, not stated.
Our handler: This is a legal terms update, not a change to the websocket orderbook or trade channels, though it governs use of the Open API.
The entry '[중요]서버 점검 안내(완료)' appeared about 12 days ago and is marked complete. The visible text contains no window, affected services or required client action. No action is needed since it has finished.
Our handler: Server maintenance could have interrupted the websocket feed, but the scope is not stated and it is already complete.
The entry '[중요] API Path 형식 및 오류 처리 방식 점검 안내' appeared about 20 days ago and is tagged Improved. No details or dates are visible. Check the full notice for whether REST path formats or error responses change. Our handler uses only the websocket, so impact is likely limited.
Our handler: Path format and error handling changes mainly concern REST endpoints, but websocket error responses might be affected; details are not shown.
The entry '[업데이트] Upbit SDK v1.1.0 - WebSocket 데이터 타입 지원 확대' appeared about 29 days ago and is tagged Improved. It concerns the official SDK, not the raw websocket protocol. No action is needed unless we use the SDK.
Our handler: This is an SDK release; our handler connects directly to wss://api.upbit.com/websocket/v1.
The entry '[안내] 자전거래 체결 방지(Self-Match Prevention, SMP) 기본값 적용 안내' appeared about 1 month ago. SMP relates to order placement, which our handler does not use. No action is needed.
Our handler: SMP concerns trading order behaviour, outside the public orderbook and trade channels.
The entry '[안내] 기술적 지표 WebSocket 지원' appeared about 2 months ago and is tagged Added. It adds a new data type; existing orderbook and trade channels are not stated to change. No action is needed.
Our handler: A new indicator data type is additive and does not change the orderbook or trade channels we use.
Only the notice title is available, with no details. Our XDP handlers carry equities data, not NYSE Bonds. No action is needed.
Our handler: NYSE Bonds is a separate market from the XDP Integrated equities feeds we consume.
Only the notice title is available. This concerns bond instruments on NYSE Bonds, not the equities feeds we use. No action is needed.
Our handler: Bond redemptions apply to NYSE Bonds, which our XDP handlers do not cover.
This is a routine halt-resumption notice for a single symbol. It would show up as a Security Status message on the XDP feed. Handlers already process these, so no action is needed.
Our handler: A trading resumption in AIRI will appear as a Security Status message on the NYSE American XDP feed.
Only the notice title is available. It points to a new symbol distribution across OPRA's multicast lines going live on November 23, 2026. Handlers that subscribe to specific multicast lines or map symbols to lines should check the full notice, update their symbol-to-line mapping, and join the November 21 confidence test.
Our handler: A change to how symbols are distributed across OPRA multicast lines affects the line subscriptions our handler uses.
The notice text gives only a headline: a test on November 20 and a production pre-launch on November 22 for NYSE Arca Extended Hours Trading. The years are not stated. It is tagged Market Data, so XDP feed traffic (security status, orders, trades) may appear outside normal hours during these sessions. Review the full notice for the exact feeds, symbols and session times, and make sure handlers tolerate messages outside regular hours.
Our handler: The notice is tagged Market Data and may change when NYSE Arca XDP feeds carry order and trade messages, but the text gives no feed details.
Only the headline is available: a new security notification for symbol ZOAR on NYSE American. No effective date or other details are given. Handlers may see a new symbol appear in Symbol Index Mapping messages for this security.
Our handler: A new NYSE American symbol could appear in Symbol Index Mapping and book/trade messages on the XDP feeds.
This concerns clearing status of bonds on NYSE Bonds. It has no impact on our equities market data handlers.
Our handler: A clearing status change on NYSE Bonds is outside the XDP feeds.
This is a routine single-symbol halt. It would be reflected as a Security Status message on the NYSE XDP feed. Handlers already process these messages, so no action is needed.
Our handler: The halt on TXR will appear as a Security Status message on the NYSE XDP feed.
New endpoints are /ws/v5/trade-sbe and /ws/v5/private-sbe, with updated XML schemas. Both require authentication and are for trading and private data. No action is needed for public market data.
Our handler: These are authenticated order-entry and private-data services, not the public books or trades channels.
The disruption began November 12 and affected email to Cboe support. Cboe asks that urgent inquiries go to the Trade Desk by phone. No market data feeds were affected and no client action is needed.
Our handler: The email vendor issue affects support communications only, not PITCH multicast market data.
Email receipt and dissemination is largely restored, with slight multi-minute delays in some cases. Cboe will only update again if severe delivery issues return. Contact the CFE Trade Desk by phone if an email inquiry gets no timely response. No market data feed changes.
Our handler: This is a corporate email vendor issue and does not touch the PITCH multicast feed or its messages.
Cboe began receiving previously delayed emails and will respond to inquiries as soon as possible. Those needing immediate help should call the CFE Trade Desk. All other Cboe systems were operating normally.
Our handler: The issue concerns email support only, not PITCH market data.
The scheduled maintenance will be postponed.
Our handler: Affects: Website, FIX, REST, WebSocket, Unified WebSocket, Embed
The Unified WebSocket streams Spot and Derivatives on one connection and selects Derivatives with asset_class=derivatives. Kraken's Rust SDK now supports Futures on it. Only clients using the Derivatives WS v1 need to migrate.
Our handler: We consume only Spot via wss://ws.kraken.com/v2, not the Derivatives WebSocket v1 host.
It covers dividends, splits, spinoffs and similar events. No action is required.
Our handler: This is a new endpoint for stock-backed derivatives, and our handler uses only spot books and trades.
The banner gives no endpoint or format changes. Feed latency and routing from the matching engine may differ, so check latency and sequence behaviour on the spot orderbook.200 stream and the REST snapshot. No client action is stated.
Our handler: The matching engine move could change latency for wss://stream.bybit.com/v5/public/spot orderbook data, though no change to it is announced.
New hosts: user-ws.kalshi.com and margin-user-ws.kalshi.com in production, with demo equivalents. They serve only per-user channels. The warp hosts keep working for now. Public market data hosts are unchanged.
Our handler: Only fill and user_orders channels move; we use the orderbook_delta channel on the external-api-ws hosts.
For these keys, balance omits the account-wide settled_funds total, so settled_funds is now optional in the response schema.
Our handler: These are account endpoints outside our public market data use.
If your FIX engine validates custom tags, load the updated FIX dictionary.
Our handler: We consume market data over WebSocket, not FIX KalshiMD.
No client change is required.
Our handler: This concerns the FIX API, which our handler does not use.
GET /markets already sends this header. Response bodies are unchanged. For real-time prices use the WebSocket ticker channel.
Our handler: REST market reads may now be up to 5 seconds stale, though we rely on the WebSocket for books.
The returned market_ticker is traded via RFQ. Unavailable requests return 409 and creation limits return 429 with specific error codes. The availability endpoint needs no authentication.
Our handler: On-request weather markets are not in the series we track.
The clarification covers how exchange indexes are listed and how subaccount balances are aggregated.
Our handler: Account balance endpoints are outside our public market data use.
HTTP statuses are unchanged. Clients that branch on too_many_requests or invalid_parameters for these cases should handle the new codes. The FIX QuoteRequestReject Text values change too.
Our handler: RFQ creation is a trading endpoint we do not use.
The error code and HTTP status are unchanged.
Our handler: This is an order-rejection error for trading, which we do not do.
The field is omitted when the algorithm is unknown.
Our handler: Key management endpoint; not part of market data.
Access is open to authenticated API users for a limited period. When the feed returns to restricted access, subscriptions without individual approval end.
Our handler: Esports score data is unrelated to the orderbook_delta channels we consume.
GET /margin/risk includes leverage and estimated liquidation prices. Public margin market endpoints accept an MCP grant for per-user rate accounting; their payloads are unchanged.
Our handler: Account-level reads for MCP clients; public margin market payloads are unchanged.
Archived settlements remain outside this endpoint.
Our handler: Account settlements endpoint; not public market data.
is_deactivated is true while the market is halted or outside its trading hours. Clients can use this to tell when a perp book is not trading. Existing subscriptions to other channels are unaffected.
Our handler: The margin market_lifecycle_v2 channel conveys trading-hours state that bears on our perpetual futures books.
Inbound email was impacted by a vendor problem. Contact the Cboe Trade Desk by phone for support. All other systems were operating normally.
Our handler: Email support issue only; no PITCH feed or message impact.
The disruption affected email support channels only. Cboe stated all other systems were operating normally. No feed or API change is involved and no client action is needed; contact the CFE Trade Desk by phone if urgent help is needed.
Our handler: The issue concerned Cboe's email vendor, not the PITCH multicast feed or any market data message.
The scheduled maintenance has been completed.
Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API
Descriptions were updated for leverage estimate and max order size endpoints. These are account and trading calculations.
Our handler: This affects account and trading endpoints for derivatives, not public market data.
This is an additive field and no client change is needed.
Our handler: The /margin/markets list we read now carries an extra minimum_quantity field.
This applies to all futures and options open interest regardless of how trades were executed, even when no trades were delayed. Affected: public/ticker, ticker.{instrument}.{interval}, get_book_summary_by_instrument/currency, public/get_order_book, get_order_book_by_instrument_id and incremental_ticker. Our handler uses get_order_book snapshots, so open_interest there is now 8 hours stale. Do not treat it as real time.
Our handler: The public/get_order_book REST snapshot we use returns open_interest, which is now delayed by 8 hours.
volume = volume_realtime + volume_delayed. Delayed volume covers Block RFQ trades executed 32 to 8 hours ago. Matching _usd and _notional breakdown fields were added to the stats object of ticker, book summary and get_order_book responses and incremental_ticker. No action is needed unless you compare volume with your own trade-based totals.
Our handler: The stats object in public/get_order_book snapshots gets new volume fields and volume semantics change.
Delayed trades are omitted from public trade history and from the trades.* and block_rfq.trades channels until published. Once published they keep their original timestamp and trade_seq, and are never applied to last_price or 24h high/low. Our handler uses only the order book channel, so it is not directly affected. Any trade-based logic should tolerate out-of-sequence trades.
Our handler: Concerns trades.* channels and trade queries, not book.<instrument>.100ms, though last_price in snapshots is unaffected by delayed trades.
Applies to public/get_tradingview_chart_data and chart.trades.{instrument}.{resolution}. Chart prices are unaffected, as before.
Our handler: Chart endpoints and channels are not used by our book handler.
Both bounds are inclusive and matched against the UTC date of each delivery. records_total reflects the filtered set.
Our handler: Delivery prices endpoint is not used by our handler.
New endpoints are GET /v5/spot-margin-trade/get-trade-auto-repay and POST /v5/spot-margin-trade/set-trade-auto-repay. These are account settings only.
Our handler: Spot margin account settings are not part of the public orderbook feed.
Classic REST Get Account Summary Info (V3) removes the subQuantity-type fields (subQuantity, spotSubQuantity, futuresSubQuantity, marginSubQuantity, optionSubQuantity and the max* variants). It adds level, maxSharedSubCount and usedSharedSubCount, which are now required. Add Sub Account (UTA and Classic) gets an optional mode field (CLASSIC or UNIFIED). The UTA WebSocket private channel FundingFeeSettle was added. All of this is account-related, so a public market data client needs to do nothing.
Our handler: Only account summary, sub-account and private WebSocket items changed; public level2 and match feeds are not involved.
books-elp becomes books-rpi, and the trading and fee parameters are renamed to their RPI equivalents. Only clients using the ELP order book channel need to change. Our handler uses the standard books channel.
Our handler: Our handler uses the books and trades channels, not books-elp or books-rpi.
trade and ticker still deliver them when the market is listed in market_tickers (or market_ids for ticker). market_lifecycle_v2 takes no market list, so it leaves them out entirely.
Our handler: Our orderbook_delta subscription covers all markets, but these on-request markets are not in the series we track.
Scoping by series_ticker, event_ticker, tickers or ticker still returns them, and mve_filter=exclude also skips them. Fetching by ticker is unchanged.
Our handler: Our GET /markets list is scoped by series_ticker, so little changes, but unscoped listings now omit KXRFQ markets.
Self-clearing accounts are not affected. The effective date is listed as TBD.
Our handler: A trading eligibility rule; we only consume public market data.
A bid is rejected above the higher of twice the best ask or best ask plus 1,000 ticks, and an ask below the lower of half the best bid or best bid minus 1,000 ticks. Empty opposite side means no limit. Rejections still return invalid price.
Our handler: This governs order entry on perps, not the public book feed.
It is fixed at the subaccount's first order in the event, so it may differ from the current netting setting.
Our handler: Portfolio position endpoints are account-level, not market data.
The field is still returned. Switch any reads of no_sub_title to yes_sub_title.
Our handler: The REST /markets list returns no_sub_title, which we should not rely on.
exchange_index on Perps is deprecated.
Our handler: These concern order-writing budgets and order groups, which we do not use.
Previously no status_reason was returned. The effective date is listed as TBD.
Our handler: Exit triggers are a trading feature.
Integer counterparts will be deprecated soon, so Clearing Member users should migrate to the _fp fields and preserve all 6 decimals in calculations.
Our handler: Clearing Member endpoints are outside the public market data we consume.
Each window sends one net delta per changed level. A connection has one orderbook_delta subscription, and a repeated subscribe must use the same interval or returns error 11. Apply deltas in seq order, apply each snapshot as a full replacement, and recover gaps with get_snapshot or resubscribe. The default behaviour is unchanged.
Our handler: This is a new option on the orderbook_delta channel we subscribe to on both venues; default is unchanged.
530=6 cancels orders from that session; 530=1 cancels only that subaccount's orders in the market. AllocAccount is optional.
Our handler: FIX order management is a trading feature.
Clients that branch on the market_closed error code on order requests should update.
Our handler: This is an order-rejection error code, not a market data field.
The verified object-array response, string price types and volume field docs were kept. Documentation only; endpoint behavior is unchanged.
Our handler: Documentation for a swap mark-price candle endpoint, not our spot channels.
Documentation correction only. No action required.
Our handler: Swap candle REST documentation, unrelated to spot depth20 and trade channels.
No details are given about the host name or limit size. If we use or plan to use a dedicated host in Tokyo, review the documented connection limits. Our current public stream host is unchanged.
Our handler: It concerns JSON market data connection limits, which could matter for our WebSocket connections, but we use the standard stream.bybit.com host.
Changes cover Submit Quote (cancelAfterMs), the new POST /v5/event/cancel-all, Get API Key Information, and Modify Master API Key. They are all trading or account related, so no action is needed for public market data.
Our handler: Quote, trading and API-key management endpoints are outside the public orderbook data we consume.
Documentation-only fix for /openApi/swap/v1/market/markPriceKlines. No action needed for a spot-only handler.
Our handler: USDT-M swap REST endpoint, not the spot WebSocket depth20 or trade channels.
Documentation clarification for /openApi/swap/v2/quote/premiumIndex. No action needed.
Our handler: Swap funding endpoint, not used by the spot handler.
Effective 2026-11-02 17:00 (UTC+8), UTA REST Get Orderbook moves to the Public rate limit pool and Public API channel. The depth parameter changes from an enum to a string, allowing other depths and FULL. Weight scales with depth: 1–20, 21–100, 101–500, and 501 or more/FULL at 250. Existing calls keep working, but request frequency should be adjusted to the new weights. Our handler uses the Classic REST level2_100 endpoint, so this only matters if we migrate to UTA.
Our handler: This changes the UTA REST order book endpoint, not the Classic /api/v1/market/orderbook/level2_100 snapshot we use.
New public swap endpoint. No action needed for spot.
Our handler: USDT-M perpetual TradFi endpoint, outside the spot market feed.
Trading-only documentation clarification for /openApi/swap/v2/trade/order. No action needed.
Our handler: Swap trading endpoint; we do no trading.
Account/trading endpoint /openApi/swap/v2/trade/fillHistory. No action needed.
Our handler: Private swap trade-history endpoint, outside public market data.
The scheduled maintenance has been completed.
Our handler: Affects: User Interface, Market Data, Bitnomial Exchange (BTNL), Order Placement
The scheduled maintenance has been completed.
Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API
The scheduled maintenance has been completed.
Our handler: Affects: Website, FIX, REST, WebSocket, Websocket API, Unified WebSocket, Embed, FIX API
Applies to the USDT-M incremental depth stream, not the spot depth20 snapshot channel. Anyone using incrDepth should rebuild from a full snapshot received on a fresh connection and subscription.
Our handler: Swap incrDepth channel; we use spot @depth20, which pushes full snapshots.
The scheduled maintenance has been completed.
Our handler: Affects: Website, FIX, REST, WebSocket, Unified WebSocket, Embed
The scheduled maintenance has been completed.
Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API
This is a new public market endpoint. Corporate actions could affect stock-linked instruments, but nothing changes for the existing spot orderbook feed. Optional to adopt.
Our handler: It is a new public /v5/market endpoint on corporate actions, but our orderbook channel and snapshot are unchanged.
Added GET /v5/spot-margin-trade/fixedborrow-interest-accrued and POST /v5/spot-margin-trade/fixedborrow-order-cancel. Account-only features.
Our handler: These are spot margin borrowing endpoints, not public market data.
They serve only those two channels and other channels return error 8. Authentication and message formats are unchanged. These hosts were later deprecated in favour of user-ws hosts.
Our handler: Only per-user channels are served; we use orderbook_delta on the existing hosts.
Handlers reading the margin market list should expect these values on settled markets.
Our handler: The /margin/markets list we read reports open interest and price differently after settlement.
An optional channel; no change to existing subscriptions.
Our handler: A new margin channel that signals market activation state relevant to perp books.
Moves funds within the subaccount between exchange indices.
Our handler: Funds transfer endpoint, not market data.
Clients that don't handle the new messages can ignore them. Child RFQs are announced as ordinary RFQs. The effective date is listed as TBD.
Our handler: RFQ communications are not part of the order book feeds we consume.
Values include initial_setup for a never-opened market and corporate_action for a corporate-action halt.
Our handler: The /margin/markets list we read gains a field that distinguishes halted from never-launched markets.
Omit them to receive all three.
Our handler: FIX market data requests; we use WebSocket.
Previously such a filter returned every order.
Our handler: Order listing is an account endpoint.
Unlike seq, clock lets you match a market's updates across redundant connections. See Orderbook Updates for ordering details. The field is additive.
Our handler: The Predictions orderbook_delta channel messages gain a clock field.
Only the title is available. This is an optional testing opportunity, and the date has already passed. It followed the earlier reminder on October 23.
Our handler: The test covers the symbol distribution across multicast lines that our handler consumes.
SBE responses were already available on the REST API without documentation. Requests for a retired schema are rejected. Retirement dates for 3:2 and 3:4 will be announced later. Our handler uses JSON, so no action is needed unless SBE is requested on the depth snapshot.
Our handler: Only matters if SBE responses are requested from the REST /api/v3/depth snapshot; the handler appears to use JSON.
A TWAP executes a total volume evenly between a start and expiry time using child orders. This is trading functionality and needs no action for market data clients.
Our handler: Trading-only Spot REST endpoints; we use no trading endpoints.
It sends a 1-level snapshot first, then a snapshot every 10 ms when the best RPI levels change. No login is required. It is optional and requires no action.
Our handler: This is a new optional channel, and our handler subscribes only to books and trades.
The scheduled maintenance has been completed.
Our handler: Affects: Gemini ActiveTrader™, Gemini Mobile App: Uptime SLA 99.95%, Exchange Trading Engine, REST API, FIX API, Websockets API
The issue affected only SIP dissemination, not PITCH. The fix is a revert, and Cboe will address the original MWCB-related issue in a future software update with advance notice from the Trade Desk. Clients relying on the SIP for Reg SHO status were affected. Our PITCH handler is not directly affected, but Trading Status handling is related.
Our handler: The issue was on the CTA SIP Reg SHO path, not PITCH, though a future BZX software update may touch status messages.
Only the title is available. Consuming handlers should review the schedule and plan to take part in failover tests, which exercise the secondary data center feed.
Our handler: Failover tests may switch the multicast feed to the secondary data center.
Only the title is available. Use these dates when planning any 2027 test activity.
Our handler: This is a testing calendar and does not change any feed, channel or message.
Existing HMAC keys are unchanged. This applies to authenticated endpoints only. Our handler uses no authentication, so nothing needs to change.
Our handler: Authentication change for signed endpoints; our market data handler uses no auth.
Trading in all products ceased at the primary site during the failover. A follow-up notice was to announce completion and resumption of trading. Market data clients should expect feed interruption and possible DR-site feed behavior during the test.
Our handler: The failover to the DR site could interrupt or change the PITCH multicast feeds for BZX, BYX, EDGX and EDGA.
All open orders were cancelled and participants should not send orders until Cboe announces trading will resume. A follow-up notice will give the resume time. Market data consumers may see a feed interruption, session or unit resets and possible connectivity differences to the DR site during the test.
Our handler: Failover to the DR site may interrupt PITCH multicast and trigger Unit Clear or session handling, though the notice does not describe feed changes.
Affiliate reporting only; no market data impact.
Our handler: Affiliate REST endpoint, unrelated to book or trade feeds.
A new error code 30035 ('You have triggered the order limit, please contact us by submitting a ticket') was added. It relates to order placement, not public market data. No action is needed for a market-data-only client.
Our handler: Order-related error code; our handler uses only public depth and aggregated deals WebSocket channels.
Resting limit orders are processed immediately. A second edit of a held order is refused with editAlreadyHeld. Cancels of held orders are answered on release. makerProtectionMillis on /instruments shows the live set. This is a trading-only change.
Our handler: Derivatives order handling and instruments metadata, not the Spot book or trade channels.
After these dates, connections to port 8443 will fail. Remove :8443 from WebSocket URLs, for example wss://ws.okx.com/ws/v5/public instead of wss://ws.okx.com:8443/ws/v5/public. The host and path stay the same, and the REST API is not affected. Until the cutoff, connections on 8443 receive a notice (event=notice) with code 64010 after the handshake, and the connection stays open.
Our handler: Our handler connects to wss://ws.okx.com:8443/ws/v5/public, which uses the discontinued port 8443, and the public-internet cutoff of 2026-10-31 has already passed.
The notice (event=notice) says WebSocket port 8443 will be retired soon and asks clients to migrate to port 443. The connection stays open. Handlers should tolerate this notice message and not treat it as an error.
Our handler: Our public WebSocket connection on port 8443 may receive this notice message.
Prefer live_data.details.status from the live data endpoints. This is a documentation clarification.
Our handler: Milestone and live data endpoints are not used by our handler.
The note describes server-side infrastructure; no client change is described.
Our handler: It concerns WebSocket session and request limits but describes no client-visible change.
They remain RFC3339 strings and agree with the _ts_ms fields.
Our handler: Affects the user_orders channel, which we do not use.
Changes include exchange_estimated_resume_time on margin exchange status and exchange_index on subaccount transfers. If you generate client types, refresh your schemas.
Our handler: Schema corrections for exchange status and transfer endpoints, not market data.
On GET /margin/funding_rates/estimate, premium_index is the premium of the final bar and premium_index_ts is that bar's last second. A bar with no sample or a halt counts as 0 under dampen and is excluded under exclude.
Our handler: Changes funding estimate semantics for perpetual futures, though we only read order books and the market list.
The report answers with 531=1, and unknown tickers are rejected with 532=1.
Our handler: FIX order management.
Messages carry SecurityTradingEvent 9 and the notice ID in tag 20190. KalshiMD sessions do not receive them.
Our handler: FIX order entry sessions; we do not use FIX.
There is no initial snapshot, and cash corporate actions are not streamed. An applied action can change positions and balances without a fill, so re-fetch them afterwards. Ticker changes may alter the symbols of perp markets we track.
Our handler: A new public margin channel announcing splits and ticker changes that could affect perp symbols.
Notices include type, status and exactly one terms object (cash, split, final_settlement or ticker_change), sorted by ex-date. Cancelled notices omit terms and execution_time.
Our handler: Scheduled corporate actions such as splits and ticker changes could affect perp markets we track.
Removed: Get Loan Market, Get Loan Market Interest Rate, Purchase, Modify Purchase, Get Purchase Orders, Redeem and Get Redeem Orders. These are margin lending and account endpoints, not market data, so no action is needed for our feeds.
Our handler: The removed Classic margin credit endpoints are outside the public spot order book and trade feeds.
Account endpoint documentation only. No action needed.
Our handler: Account endpoint /openApi/account/v1/uid, outside public market data.
Promotional activity data, unrelated to market data feeds.
Our handler: Activity endpoint, not an order book or trade channel.
These are authenticated referral and account endpoints under /v5/referral. No action is needed.
Our handler: Referral endpoints are account-related and unrelated to public market data.
Account-side activity data. No action needed.
Our handler: Private activity endpoint, outside market data.
Agent/partner endpoint. No action needed.
Our handler: Agent reward endpoint, unrelated to market data.
Documented under USDT-M perpetual contracts. Our spot @trade channel shares the name, but the notice does not mention spot. If the spot stream gains the field, a strict parser should tolerate an extra string field t.
Our handler: The @trade channel is named the same as ours, but the change is listed for USDT-M perpetuals only.
Documentation change for public REST market data. Our WebSocket handler already uses no auth, so no action is needed.
Our handler: Covers public spot market data docs, though our handler uses only the unauthenticated WebSocket channels.
Repeated failures can temporarily rate limit new quotes.
Our handler: RFQ quoting is a trading feature.
Calls above the rate return 429, and balance calls no longer draw on the Read budget.
Our handler: Account balance endpoint.
Public market, event and series reads accept an MCP grant for per-user rate accounting with unchanged payloads. Use GET /markets with event_ticker, limit and cursor for outcome pages.
Our handler: Mostly account access; the event option is additive and we do not use the events endpoint.
The response has one entry per ticker in request order with the same bids and asks levels as the single-market endpoint. A non-margin ticker returns 404.
Our handler: A new REST way to read perp order books, though we use the WebSocket.
HTTP status 400 and the code are unchanged. When specific markets are at fault, details lists their tickers.
Our handler: Combo market creation is a trading endpoint.
dampen counts a second with no premium as 0 in the funding average, while exclude leaves it out.
Our handler: The /margin/markets list we read gains a new field.
These values are configured at creation and do not reflect later clearing configuration changes.
Our handler: The /margin/markets list we read, including its funding cap, gains new fields.
Reuse it only for identical retries. It is not supported for transfers involving numbered subaccounts.
Our handler: Funds transfer endpoint.
Existing cursor pagination, timestamp filters and page limits still apply.
Our handler: Margin public trade data endpoint gains a broader query option.
An additive field; no client change is needed.
Our handler: The /margin/markets list we read gains a new field.
This affects Cboe's internal NBBO calculation inputs for BZX, BYX, EDGA and EDGX. No change to PITCH message formats or channels was announced and no client action is needed.
Our handler: This is an internal NBBO input change and does not alter PITCH messages.
A new public market endpoint covering linear and option categories only. Spot is not covered, so no action is needed.
Our handler: It covers linear and option instruments, while we consume spot only.
These enum values apply to private execution and transaction-log data for stock splits. No market data impact.
Our handler: These are private execution and transaction-log enums, not public orderbook fields.
Each pair such as btc_usd and btc_usdc has its own budget of 16 groups. Trading-related only.
Our handler: MMP configuration is an account/trading feature.
The ofs parameter is superseded and must be absent or 0 when with_cursor is true. Account endpoint only.
Our handler: Private Spot REST Ledgers endpoint; we use no account endpoints.
They may offer better performance as requests pass through fewer infrastructure layers. Optionally use them as fallback hosts for the depth snapshot request if the base endpoint has issues. No action is required.
Our handler: Alternative hosts for the REST snapshot at api.binance.us/api/v3/depth that could serve as fallbacks.
Both use the Query affiliate participants API key permission and signed Affiliate REST authentication. No market data impact.
Our handler: Affiliate endpoints, unrelated to market data.
Read makerProtectionMillis on /instruments for the live set. Trading-only.
Our handler: Derivatives order handling, not Spot market data.
Deprecated: ofs on TradesHistory, ClosedOrders and Ledgers; aclass on Ledgers; trades on QueryLedgers. Added fields on order and trade info and CreditLines. All affected endpoints are private account endpoints.
Our handler: Private Spot REST account and order endpoints, not used by our WebSocket market data handler.
OKX may switch more scenarios to incremental pushes without notice. Clients should update their instrument cache by instId and not assume every push is a full set.
Our handler: This matters only if we use the instruments channel to maintain a symbol list; our described channels are books and trades.
Requests and subscriptions using a delisted Crypto-USD instId may fail or return no data, and there is no automatic mapping. Use the Crypto-USDC instrument IDs instead and update instrument caches and subscriptions. A new Activate feature endpoint and error code 54109 were also added for trading.
Our handler: Subscriptions to books and trades for any Crypto-USD spot symbol, and the REST books snapshot, must move to the USDC instIds.
The endpoints are overview, assessment details and performance history. They are account-related and need no action.
Our handler: These are authenticated account endpoints, not public market data.
It is additive and limited to linear and inverse. Spot responses are not stated to change. The same date adds batch tax report export endpoints, which are account-only.
Our handler: The new tags field applies to linear and inverse instruments, not spot, and we do not use the instruments endpoint.
GET /v5/market/option-base-coins and GET /v5/ins-loan/delay-liq-status are new. The Netherlands domain is removed from the docs. Clients that use that regional domain should switch to the main hosts. Our handler uses api.bybit.com and stream.bybit.com.
Our handler: Option and institutional loan endpoints are unrelated to our spot orderbook feed and we do not use the Netherlands domain.
Classic REST Get Symbol and Get All Symbols add assetClass and subMarketType, and the status field's marketType value is deprecated in favour of them. No removal date is given. If our symbol reference-data loader reads marketType, plan to switch to assetClass and subMarketType.
Our handler: Classic Get Symbol and Get All Symbols are market reference data that may be used for BTC-USDT symbol discovery.
UTA REST Get Trade History adds fillPnl, and the UTA WebSocket Execution channel adds fP. FillPnl data before 2026-09-05 (UTC-8) returns an empty string. Place Order, Get Order Details and the UTA WebSocket Order channel add brokerTag (up to 50 characters). Error code 116241 was added for positions that have hit the system risk limit. All of these are trading or account items.
Our handler: These are private UTA trading, execution and order interfaces, not public market data.
Affected are POST/PUT/DELETE /api/v3/userDataStream and the WebSocket API userDataStream.start/ping/stop methods. A new userDataStream.subscribe.signature method was added to the WebSocket API. This concerns account data only, and our public streams are not affected.
Our handler: Only user data streams are affected; our depth and trade streams are public.
Only the title is available. It follows earlier notices on June 1, June 15 and August 14. Handlers should check the new session times against their session-handling and end-of-day logic.
Our handler: Changed OPRA hours affect when Last Sale and quote messages and control messages are sent.
Thresholds are 500 USD for spot, 2,000 USD for futures and 5,000 USD for swap. This applies to trading operations only.
Our handler: This affects order placement and amendment, not public market data.
Affects user.changes.{kind}.{currency}.{interval} and user.changes.{instrument_name}.{interval}. Private channels only.
Our handler: Private user.changes channels are not used by our public-data handler.
This applies to POST and GET /api/v3/capital/transfer and the tranId query. These are account and wallet endpoints. No action is needed for a public market data client.
Our handler: Account transfer endpoints (/api/v3/capital/transfer) are not used by our public market data handler.
The instruments change applies only to category=option. The order change is trading-only.
Our handler: The change covers option instruments info and order placement, not spot orderbook data.
The fields stay present with array type but carry no data. Use GetTradeVolume with fee_schedule=true for fee information. Only matters if reference data is read from REST AssetPairs.
Our handler: AssetPairs is public Spot reference data; our handler uses only WS v2 but any REST pair-metadata fee use would be affected.
Adds makerProtectionMillis to /instruments and /trading/instruments. Post-only placements and cancellations are not held. Available in UAT from 27 August 2026. Trading-only.
Our handler: Derivatives order handling and instrument metadata, not Spot book or trade channels.
Only the title is available. A new trading session identifier is introduced alongside the hardware upgrade, which may change message content. Check the specification and test before activation.
Our handler: A new trading session identifier may change the format or content of the messages our handler decodes.
This applies to those internal accounts only. Our handler already uses api.bybit.com and stream.bybit.com with no auth, so nothing changes.
Our handler: It targets specific internal accounts and uses the same hosts we already use.
Account endpoint behavior change. No action needed.
Our handler: Private swap positions endpoint.
The message tells clients to try again later. No endpoint or field changes. Handlers should treat it as a retryable error if it appears.
Our handler: This is a documented error code only, with no change to the Classic spot channels or snapshot endpoint we use.
This is a new product API. No action is needed for the spot orderbook feed.
Our handler: Event Contracts are a new product separate from the spot orderbook channel.
The issue was resolved by 14:39 ET on September 2. It concerned order entry sessions, and no market data impact was reported.
Our handler: The issue affected TCP order entry sessions, not PITCH multicast.
The changes are additive and the existing system status field is unchanged. Clients not reading the new fields are unaffected. Optionally subscribe to the status channel or poll MaintenanceSchedule to wind down ahead of maintenance windows.
Our handler: Adds fields to the WS v2 status channel on the same host we use; we subscribe only to book and trade, so nothing breaks.
PendingOpen applies to Futures in Get Instruments Info and Get Account Instruments Info, and orders cannot be placed until the status becomes Trading. The other changes are account related.
Our handler: The new status applies to Futures instruments, not spot.
Any parser that reads the buyer order ID (b) or seller order ID (a) fields from trade messages must stop depending on them. Update the trade message schema and make parsing tolerant of their absence.
Our handler: The <symbol>@trade channel payload we consume no longer contains the buyer and seller order ID fields.
Review the handler's snapshot-and-diff synchronization against the updated procedure. A limit of 5000 is now documented for the snapshot, whereas we use 1000.
Our handler: Affects the @depth diff stream and the REST /api/v3/depth snapshot synchronization procedure we use.
Our snapshot uses /api/v3/depth, so it is unaffected. Verify that no component still calls any /api/v1 endpoint.
Our handler: Our snapshot uses /api/v3/depth, but any leftover /api/v1/depth use would break.
The parameter is optional, and omitting it keeps the current behavior. No change is needed unless you want to use it.
Our handler: Optional new parameter on the REST depth snapshot endpoint we call.
These add region-specific access methods. Our handler uses the global hosts and needs no change.
Our handler: Regional access guidance does not change our host wss://stream.bybit.com or the REST snapshot.
Documentation clarification for the swap endpoint. No action needed.
Our handler: Swap funding rate REST endpoint.
The fields are additive. Also added: netDeltaRatio in Get Position Info and the WS Position stream, and currcCursor on Funding Account Transaction History. None affect the orderbook feed.
Our handler: The new instrument fields could appear for stock symbols in instrument metadata, but our orderbook channel and snapshot are unchanged.
Changes include renamed fields (hold to locked, chainId to chain, UID to uid), the Flex Transfer transferType replacement, and Get Symbol enum updates. Get Klines gains klineType, Get Index Price symbol fixes, and new UTA endpoints Amend Order, All Funding Fee Rates and Get Current Funding Rate were added. The UTA WebSocket Funding Fee channel gains a symbols request field and an lfr response field. Anyone on UTA must migrate to the V2 URLs. Our handler uses Classic spot endpoints, which are not covered.
Our handler: The V2 upgrade covers UTA REST and WebSocket only, while we use Classic /market/level2 and /market/match with the Classic REST snapshot.
The change is for options order entry. Also added are Universal Transfer List filters and new fields.
Our handler: Order entry and transfer endpoints are outside public market data.
This changes the inputs to Cboe's NBBO calculations only. No change to PITCH formats was announced and no client action is needed.
Our handler: This is an internal NBBO input change and does not alter PITCH messages.
The endpoint needs the SPOT_ACCOUNT_READ permission and has IP weight 1. It is an account endpoint. No action is needed for a market data client.
Our handler: Account/API key endpoint; we use no authenticated endpoints.
Affects authenticated requests only. Our feeds need no signing.
Our handler: Signed REST requests; our WebSocket market channels use no auth.
Applies to off-book fills such as liquidation assignments and RFQ offers. Master accounts only. Trading and account feature.
Our handler: Derivatives account and assignment endpoints, unrelated to market data.
This applies to the private Order channel. The effective date for post_only and mmp_and_post_only orders is 2026-08-20 in production.
Our handler: This affects the private Orders channel, which our handler does not use.
These are private execution and broker data changes.
Our handler: They affect private execution and broker endpoints, not public orderbook data.
UTA REST Get Trade History returns size as positive for fillType ADL, LIQUID or SETTLEMENT. The UTA WebSocket Execution channel does the same for q. Classic REST Exchange Broker adds Set Markup Fee and Get Markup Fee. None of these are public market data.
Our handler: These are private UTA execution data and broker endpoints, not public order book or trade feeds.
Only the title is available. The test date has already passed.
Our handler: The test covers the symbol distribution across multicast lines that our handler consumes.
Thresholds are 10,000 USD for SWAP and FUTURES and 1,000 USD for spot. Orders already on the book are unaffected. This applies to trading operations only.
Our handler: This affects place and amend order operations, not public market data.
This is a response shape change on an account endpoint.
Our handler: Asset Overview is an account endpoint that we do not use.
For example, VIP0 goes from 200/s to 300/s, VIP4 from 500/s to 750/s, and VIP12 from 3000/s to 4000/s. This is a limit increase for UTA REST, so no client action is needed.
Our handler: This applies to the UTA REST resource pool, not the Classic public endpoints we call.
Affects get_account_summary, get_account_summaries, simulate_portfolio and user.portfolio.{currency}, only for segregated_sm accounts.
Our handler: Account and portfolio endpoints are outside our public market data use.
Routed instruments show is_cbe_routed: true. Spot trade queries and trades.*/chart.trades.* subscriptions return or are rejected with error 11060, and volume_notional/volume_usd are omitted for routed spot. Order book data is unaffected. Derivatives are unaffected.
Our handler: We consume perpetual futures books; routed spot and derivatives are unaffected and order book data is unchanged.
Only the title is available. It relates to the GTH hardware upgrade, which activates August 23, 2026 per the March 4 notice.
Our handler: GTH system changes may affect the early-session OPRA feed.
The sample response was updated. These are additive fields. Our handler does not use the REST exchangeInfo endpoint as described, but strict parsers of this endpoint should tolerate the new fields.
Our handler: exchangeInfo is symbol metadata; we do not list it among the endpoints in use but it could feed symbol reference data.
This is the aggregated deals channel our handler subscribes to ([email protected]@100ms@{SYMBOL}). The new field is additive. Ensure the protobuf decoder tolerates the unknown field; no action is required unless you want to use it.
Our handler: Touches the [email protected] channel we consume for aggregated trades.
Get Trade History returns an empty liquidityRole instead of MAKER when fillType is ADL. Get Position List (UTA) adds updateTime. Classic Add and Modify sub-account API require ipWhitelist if the permissions include Transfer (Withdraw), and otherwise it is optional. All of these are account endpoints.
Our handler: These are private trading and account endpoints, outside public market data.
This also governs the depth shown on the books-rpi order book. There are no endpoint, parameter or error code changes.
Our handler: It affects RPI order placement and the books-rpi channel, which we do not use.
This extends the full-depth feature to futures. Spot support was added earlier. Other changes that day: Transaction Log displayType and DIVIDEND_SETTLEMENT, and Airdrop Products fields.
Our handler: It extends the full depth orderbook to Futures, while we use spot orderbook.200.
Affects private/get_position and private/get_positions. Still available through Position Builder.
Our handler: Private position endpoints are not used.
This is due to integration with Starbase. Deribit expects no major performance degradation. We use the 100ms book channel, not .raw, so no action is needed unless .raw channels are adopted.
Our handler: Affects .raw market data subscriptions; we use book.<instrument>.100ms, which is not .raw.
Fields include starbase_client_order_id, starbase_order_id, starbase_match_id and starbase_timestamp. Mostly private objects.
Our handler: These fields are on private order, trade and transaction log objects.
product_group is BTC, ETH, TIER_2 or TIER_3. index_id is the numeric ID of the price index. Additive; no action is needed.
Our handler: Additive fields on instrument metadata endpoints, which our handler does not rely on.
These are account and lending changes.
Our handler: They are crypto loan endpoints unrelated to market data.
Clients using this endpoint must limit each query to the new maximum range.
Our handler: Our handler uses live books and trades and the REST books snapshot, not the historical market data endpoint.
Also: Move Position supports TradFi perpetuals, and Switch Position Mode supports one-way and hedge modes for more contract types. Private order data only.
Our handler: The type change is on private order endpoints and streams, not the public orderbook channel.
These affect trading and account settings only.
Our handler: They are trading and account rules, not public market data.
Requests containing these parameters across Spot, Margin, Futures and Copy Trading order endpoints are rejected with error 400413. New UTA REST endpoints: Get Sub-account List, KCS Fee Deduction Management, Get Deposit History and Get Withdrawal History. These are trading and account items.
Our handler: Only order placement and account endpoints are affected; the public order book and trade feeds are unchanged.
Get Account Instruments Info changes the meaning of isPublicRpi and myRpiPermission. Other changes cover Create RFQ, Create/Execute Quote, Get RFQs and Get Coin Delta Amount. All are authenticated.
Our handler: These are account instrument and RFQ endpoints, not public orderbook data.
Our 1000-level snapshot now costs 50 weight. Review how often snapshots are requested, as resyncs across many symbols consume more of the budget. The weights of trades and aggTrades increased too.
Our handler: The REST snapshot /api/v3/depth?limit=1000 now costs 50 weight.
Previously pings were every 3 minutes with a 10-minute pong timeout. Ensure the client answers pings promptly; most libraries do this automatically.
Our handler: Applies to our connection on wss://stream.binance.us:9443 for the depth and trade streams.
On receipt, open a new connection as soon as possible to avoid interruption. Handle this unknown message type without error and trigger a reconnect, including resync of the order book.
Our handler: May arrive on the WebSocket connection carrying our streams and should be handled as a reconnect signal.
Read permissionSets instead of permissions if you use them for symbol filtering. The permissions field will be removed later. Not used by our depth snapshot or streams as described.
Our handler: Only relevant if exchangeInfo permissions are used for symbol discovery.
These concern trading and account features, not public market data.
Our handler: Trading, account and user data stream changes outside our public depth and trade feed.
REST change. Our handler uses the WebSocket @trade channel, so nothing changes for it. Any REST trade backfill should move to the v2 path and drop the removed parameters.
Our handler: Spot REST trades endpoint; we use the @trade WebSocket channel, but a REST fallback could be affected.
REST change. No impact on our WebSocket depth and trade channels.
Our handler: Spot kline REST endpoint, which we do not consume.
REST change. No action needed for our WebSocket handler.
Our handler: Spot ticker REST endpoint, which we do not consume.
REST change. Our handler gets the book via the @depth20 WebSocket channel. Any REST depth snapshot fallback must use the new path, the limit parameter and the required type.
Our handler: Spot REST depth endpoint; we use @depth20 over WebSocket, but a REST book fallback could be affected.
REST change. No impact on our WebSocket channels.
Our handler: Spot price REST endpoint, which we do not consume.
REST change. No impact on our @depth20 and @trade channels.
Our handler: Spot best bid/ask REST endpoint, which we do not consume.
REST change. No action needed.
Our handler: Spot historical kline REST endpoint, which we do not consume.
REST change. Our live trade feed is the @trade WebSocket channel, which is unaffected.
Our handler: Spot historical trades REST endpoint, which we do not consume.
These are product and account endpoints. No action is needed.
Our handler: They are launch-event product endpoints unrelated to the orderbook feed.
Only the titles are available. The tests have already passed. A further RTH hardware upgrade and session identifier test #1 reminder was updated on July 30, and test #2 was set for August 22.
Our handler: Hardware upgrades and the new session identifier may affect the feed our handler reads.
Japan region users should use the updated domains. Our handler uses the global api.bybit.com and stream.bybit.com hosts, so this does not apply unless we serve Japan-region access.
Our handler: It changes API domains for Japan region users, while our handler uses the global hosts.
It was later replaced on 2026-08-20 by ForwardSplitSettle and ReverseSplitSettle. Private execution data only.
Our handler: execType appears on private execution data, not public market data.
This applies to the order entry feed only.
Our handler: Fast Order Response is a trading-side stream, not public orderbook data.
New fields: starbase_match_id, starbase_timestamp, starbase_order_id, starbase_last_update_timestamp. No action needed.
Our handler: Private method and private trade/order object fields.
Only the title is available. Check the notice for the test date and whether a feed switch to the secondary data center is involved.
Our handler: Business continuity tests can involve disaster recovery feed switching.
This relates to wallet withdrawals only. No action is needed for a market data client.
Our handler: Withdrawal error code; outside public market data channels.
The endpoint needs an API key and signature. Each successful call creates a new address, and retries may create several. It returns error 10703 when the address limit is reached. It is a wallet endpoint and does not touch public market data, so no action is needed for our depth and trade handlers.
Our handler: Authenticated wallet endpoint /v2/supplement/add_deposit_address.do is outside the public depth and trade WebSocket channels we consume.
Only the notice title is available. The change alters how symbols are spread across multicast lines, with go-live on November 23, 2026. Plan for testing and for any line-mapping updates ahead of that date.
Our handler: Symbol-to-multicast-line distribution determines which lines our handler must consume.