Feeds / Changes

Feed changes

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

334 changes24 sourceslast check 2026-11-21 23:17 UTC

Upcoming

2026-11-23

OPRA (consolidated US options)

New OPRA Dynamic Rebalance Symbol Distribution: confidence test Nov 21, activation Nov 23, 2026
Action needed
2026-11-23

OPRA (consolidated US options)

Dynamic Rebalance Symbol Distribution: industry tests and go-live Nov 23, 2026
Action needed
2026-11-30

Kraken

Derivatives: POST /withdrawal and GET /transfers deprecated, removal 30 November 2026
Action needed
2026-12-10

Upbit

Open API Terms of Use revision (effective 12/10)
Action needed
2027-03-01

Kraken

Derivatives WebSocket v1 deprecated; unavailable from 1 March 2027
Action needed

All changes

2026-11
2026-11-26InfoNew endpoints for on-request flight disruption marketsKalshi Events Kalshi Perps
Kalshi added three endpoints for on-request flight markets (series starting KXRFQFLIGHT) that pay out when a flight is canceled, delayed, or either. They cover creating a market, checking availability, and looking up flights.
Details

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.

Source ↗

2026-11-21MaintenanceUS Derivatives MaintenanceKrakenMay affect market data
Scheduled 00:30 to 02:00 UTC (Market Data, Bitnomial Exchange (BTNL), Order Placement).
Details

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

Source ↗

2026-11-21InfoPer-account 24-hour limit on creating flight disruption marketsKalshi Events Kalshi Perps
The on-request endpoint POST /flight_disruption_markets now caps how many new markets one account can create in a rolling 24 hours, in addition to the existing limit across all users.
Details

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.

Source ↗

2026-11-20InfoResponse field now supports a futures symbol typeKuCoinMay affect market data
A response field of an API now supports a new symbol type for futures, where previously only spot was supported.
Details

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.

Source ↗

2026-11-20InfoNew small-balance to KCS conversion endpointsKuCoin
KuCoin added endpoints to list convertible small balances, convert up to 20 currencies into KCS, query a conversion order and fetch conversion order history.
Details

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.

Source ↗

2026-11-20InfoAPI rate limit pool change in ManagementKuCoinMay affect market data
The changelog lists an api-rate-limit-pool change under Management, with no details given.
Details

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.

Source ↗

2026-11-20InfoUTA API V2 addedKuCoin
KuCoin added a Unified Trading Account (UTA) API V2.
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.

Source ↗

2026-11-20Action neededError code 111235 replaces 111202 and 111209KuCoinMay affect market data
A new error code 111235 (Service busy, reduce request frequency and retry later) replaces codes 111202 and 111209, which will be deprecated.
Details

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.

Source ↗

2026-11-20InfoEndpoint now accepts up to 100 comma-separated market tickersKalshi Events Kalshi PerpsMay affect market data
A query parameter now accepts up to 100 comma-separated market tickers, and a single ticker still works. The text does not name the endpoint.
Details

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.

Source ↗

2026-11-20InfoNew endpoint: Query Card ListBybit
Bybit added a new endpoint to query the Bybit card list.
Details

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.

Source ↗

2026-11-20InfoNew endpoint: Query Card LimitBybit
Bybit added a new endpoint to query the Bybit card limit.
Details

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.

Source ↗

2026-11-20InfoRFQs on request-created markets always obscure creator IDKalshi Events Kalshi Perps
RFQs on markets created on request (such as weather point markets), or on combos made entirely of such markets, now hide the creator's public communications ID regardless of the obscure_creator_id setting. Other users see a shared placeholder until a successful execution.
Details

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.

Source ↗

2026-11-20MaintenanceScheduled maintenance - Trading Services UpgradeGeminiMay affect market data
Scheduled 03:00 to 03:30 UTC (Exchange Trading Engine).
Details

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Our handler: Affects: Exchange Trading Engine

Source ↗

2026-11-20InfoNYSE Arca: new trading session indicator on execution reports and invoicesNYSE XDP
NYSE Arca is adding a trading session indicator to execution reports and invoices. The notice is tagged Trading and Post Trade.
Details

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.

Source ↗

2026-11-20InfoNYSE American Equities: trading resumption in GNSNYSE XDPMay affect market data
Trading is resuming in the symbol GNS on NYSE American Equities. Only the headline is given, with no further details.
Details

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.

Source ↗

2026-11-20MaintenanceSpot and Unified WebSocket MaintenanceKrakenMay affect market data
Scheduled 13:25 to 13:40 UTC (WebSocket, Unified WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: WebSocket, Unified WebSocket

Source ↗

2026-11-20InfoNYSE Pillar Options Common Client Specification updatedNYSE XDP
NYSE published an update to the Pillar Options Common Client Specification for NYSE American Options and NYSE Arca Options. The notice lists trading, post trade and market data as areas covered.
Details

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.

Source ↗

2026-11-20InfoRaw subscriptions merge changes over at least 10 msDeribiteffective 2026-11-24May affect market data
Notifications on raw subscriptions will be sent at most once every 10 ms, with changes inside that window merged into one notification. Under heavy traffic, raw notifications can arrive up to about 15 ms later than before.
Details

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.

Source ↗

2026-11-20InfoNew 'swaps' value for subaccount_type on margin balance, position and risk rowsKalshi Events Kalshi Perps
The subaccount_type field on margin balance, position and risk rows gains a new value, 'swaps'. It denotes a cross-margined wallet for trading event contracts on the margin exchange, identified by a swaps code from 1 to 63.
Details

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.

Source ↗

2026-11-20InfoOrders now rejected for markets closing within 24 hoursKalshi Events Kalshi PerpsMay affect market data
The changelog text is garbled, but it appears that order requests for a market whose close time is 24 hours away or less now return an error instead of being accepted. The market itself stays open and unchanged until its close_time.
Details

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.

Source ↗

2026-11-20InfoOrder endpoints now validate required fieldsKalshi Events Kalshi Perps
Create Order, Amend Order and Batch Create Orders now check a required field alongside other required fields. Omitting it returns a missing_parameters error, and an invalid value returns another error code.
Details

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.

Source ↗

2026-11-20InfoNew markets must start more than 7 days out (previously 24 hours)Kalshi Events Kalshi PerpsMay affect market data
The text says a new market's show must now start more than 7 days from now, where 24 hours used to be enough. The excerpt is fragmentary, and the full change is unclear.
Details

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.

Source ↗

2026-11-20InfoNYSE Options: Changes to Quarterly Bid/Ask Differentials - ANTNYSE XDP
NYSE posted a notice about changes to quarterly bid/ask differentials for NYSE Options. The notice text gives no further details or dates.
Details

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.

Source ↗

2026-11-19InfoDerivatives: POST /transfer supports Spot wallet; GET /transfer/assets addedKraken
From 19 November 2026 (moved from 17 November) Futures POST /transfer can move funds to and from the Kraken Spot wallet. A new GET /transfer/assets lists transferable assets and limits.
Details

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.

Source ↗

2026-11-19Action neededDerivatives: POST /withdrawal and GET /transfers deprecated, removal 30 November 2026Krakeneffective 2026-11-30
POST /withdrawal and GET /transfers will be removed on 30 November 2026. Integrations should move to POST /transfer.
Details

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.

Source ↗

2026-11-19InfoDerivatives: new Maker Protection hold-cap error and cancelallorders trigger eventsKraken
Requests refused by the Maker Protection concurrent-hold cap now return a dedicated error. POST /cancelallorders now returns CANCEL events for cancelled trigger orders.
Details

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.

Source ↗

2026-11-19Action neededEmpty market_id and clock 0 in orderbook_snapshot for markets with no changeKalshi Events Kalshi PerpsAffects our handler
An orderbook_snapshot for a market with no recorded change, such as a new market with no orders yet, can now have an empty market_id and a clock of 0.
Details

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.

Source ↗

2026-11-19InfoInvalid NUL or non-UTF-8 request bytes now return 400Kalshi Events Kalshi Perps
Requests with a NUL byte or invalid UTF-8 in the path or query now return 400 invalid_parameters instead of 500.
Details

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.

Source ↗

2026-11-19InfoOn-request concert cancellation market endpoints addedKalshi Events Kalshi Perps
Four new Predictions REST endpoints create and list on-request concert markets (series starting KXRFQCONCERT) that pay on postponement or cancellation.
Details

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.

Source ↗

2026-11-19InfoRate limit headers added to REST responsesKalshi Events Kalshi PerpsMay affect market data
REST responses now carry X-RateLimit-Limit, -Remaining, -Reset and -Cost headers describing the bucket charged.
Details

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.

Source ↗

2026-11-19Infoexpected_expiration_time capped at latest_expiration_timeKalshi Events Kalshi PerpsMay affect market data
On Predictions market objects, expected_expiration_time is now capped at the market's latest_expiration_time.
Details

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.

Source ↗

2026-11-19BreakingDeprecated expiration_time removed from Predictions market objectsKalshi Events Kalshi PerpsAffects our handler
The expiration_time field is removed from market objects, including markets nested in events. Use latest_expiration_time instead.
Details

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.

Source ↗

2026-11-19InfoEquities perps overnight price band and SettlementBoundsCancelKalshi Events Kalshi PerpsMay affect market data
During the overnight session (8 PM to 4 AM ET), equities perps orders must be priced within 20% of the prior 4 PM ET settlement price.
Details

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.

Source ↗

2026-11-19InfoGET /incentive_schedules added; incentive programs gain filtersKalshi Events Kalshi Perps
A new public endpoint lists recurring incentive schedules, and GET /incentive_programs gains series_ticker and event_ticker filters.
Details

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.

Source ↗

2026-11-19MaintenanceDerivatives Platform MaintenanceKrakenMay affect market data
Scheduled 08:00 to 08:15 UTC (User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API).
Details

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

Source ↗

2026-11-19MaintenanceKraken Prime API (REST, FIX, WebSocket) MaintenanceKrakenMay affect market data
Scheduled 21:00 to 21:15 UTC (FIX, REST, WebSocket).
Details

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

Source ↗

2026-11-19InfoWeather point markets can span midnight via optional end_dateKalshi Events Kalshi Perps
Kalshi's on-request weather point market creation now accepts an optional end_date, so a window can run from one local day into the next (e.g. 11pm to 3am). Requests without end_date behave as before.
Details

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.

Source ↗

2026-11-19MaintenanceUnified WebSocket API now available for DerivativesKrakenMay affect market data
Scheduled 11:00 to 23:59 UTC (Websocket API, Unified WebSocket).
Details

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

Source ↗

2026-11-19InfoNYSE American: trading resumption in FMBMNYSE XDPMay affect market data
NYSE American announced that trading resumes in the symbol FMBM. The notice gives no further detail.
Details

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.

Source ↗

2026-11-19InfoNYSE Arca Equities: trading resumption in 11 ProShares ETFsNYSE XDPMay affect market data
NYSE Arca announced that trading resumes in 11 ProShares ETFs. The notice gives no further detail.
Details

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.

Source ↗

2026-11-19Action neededLower rate limit for ticker and order book REST methodsDeribitAffects our handler
A new shared limit of 5 requests per second (burst 25) now applies to the ticker and order book methods combined. Requests over the limit fail with too_many_requests (10028).
Details

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.

Source ↗

2026-11-19InfoWeather point markets now described in the location's time zoneKalshi Events Kalshi Perps
New weather point markets show their title and rules in the time zone of the location, which Kalshi derives from the coordinates. Requests, responses and tickers are unchanged, and existing events keep their current description.
Details

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.

Source ↗

2026-11-19InfoRFQ sessions can use listener modeKalshi Events Kalshi Perps
KalshiRFQ sessions can now choose listener mode with ListenerSession<20126>=Y. The session keeps quoting and also receives the account's execution reports, including fills of accepted quotes.
Details

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.

Source ↗

2026-11-19InfoNYSE Bonds: new bond listing MCO33NYSE XDP
NYSE announced a new bond listing with the symbol MCO33.
Details

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.

Source ↗

2026-11-19InfoNYSE Bonds: new bond listings BBVA29E, BBVA29F and BBVA36ANYSE XDP
NYSE announced new bond listings with the symbols BBVA29E, BBVA29F and BBVA36A.
Details

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.

Source ↗

2026-11-19InfoTravel Rule deposit APIs addedOKX
OKX added two endpoints for viewing locked Travel Rule deposits and unlocking them, plus new funding error codes 58385-58389.
Details

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.

Source ↗

2026-11-18InfoWeather market location no longer snapped to NOAA MRMS grid cell centerKalshi Events Kalshi Perps
A market's location is now the requested latitude and longitude rounded to three decimal places (about 100 m), not the center of the NOAA MRMS grid cell. Requests share a market only if their coordinates match to three decimals.
Details

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.

Source ↗

2026-11-18InfoNYSE American Equities - Trading Resumption in ZOARNYSE XDPMay affect market data
NYSE American announced that trading resumed in the security ZOAR following a regulatory halt. No technical or protocol changes are described.
Details

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.

Source ↗

2026-11-18InfoNYSE American: Initial Pricing Regulatory Halt for symbol FMBMNYSE XDPMay affect market data
NYSE American posted a notice of an initial pricing regulatory halt in the symbol FMBM. The notice gives only a time of 11:25 AM and no further detail.
Details

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.

Source ↗

2026-11-18InfoNew swap chart-supported symbols endpointBingX
BingX added /openApi/swap/v1/quote/chartSymbols to look up chart-supported symbols.
Details

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.

Source ↗

2026-11-18InfoNew swap liquidation heatmap endpointBingX
BingX added /openApi/swap/v1/liquidation/heatmap for liquidation heatmap queries.
Details

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.

Source ↗

2026-11-18InfoNew swap liquidation levels endpointBingX
BingX added /openApi/swap/v1/liquidation/levels for liquidation price distribution queries.
Details

New perpetual swap analytics endpoint. No action required.

Our handler: Swap analytics REST endpoint, not used by our spot WebSocket handler.

Source ↗

2026-11-18InfoNew swap open interest history endpointBingX
BingX added /openApi/swap/v1/openInterest/history for open interest history queries.
Details

New perpetual swap data endpoint. No action required.

Our handler: Swap REST endpoint; we consume only spot WebSocket channels.

Source ↗

2026-11-18InfoNew swap liquidation statistics endpointBingX
BingX added /openApi/swap/v1/liquidation/statistics for long and short liquidation amount statistics.
Details

New perpetual swap statistics endpoint. No action required.

Our handler: Swap REST endpoint, outside our spot depth and trade channels.

Source ↗

2026-11-18InfoNew swap long/short ratio history endpointBingX
BingX added /openApi/swap/v1/longShortRatio/history for long/short ratio history queries.
Details

New perpetual swap data endpoint. No action required.

Our handler: Swap REST endpoint, not used by our spot handler.

Source ↗

2026-11-18InfoMark-price candle documentation correctedBingX
Docs for swap mark-price candles now describe corrected candle times, calendar months, timeZone, inclusive bounds and four time-range query modes.
Details

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.

Source ↗

2026-11-18InfoSwap recent trades limit enforcement documentedBingX
The swap /openApi/swap/v2/quote/trades docs now state limit rules: omitted or 0 defaults to 500, maximum 1000, invalid values return error 109400.
Details

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.

Source ↗

2026-11-17MaintenanceWebSocket and FIX API MaintenanceKrakenMay affect market data
Scheduled 09:30 to 14:30 UTC (FIX, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, WebSocket

Source ↗

2026-11-17MaintenanceDerivatives Platform MaintenanceKrakenMay affect market data
Scheduled 08:00 to 09:00 UTC (User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API).
Details

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

Source ↗

2026-11-17MaintenanceKraken Website and API MaintenanceKrakenMay affect market data
Scheduled 08:01 to 08:16 UTC (Website, FIX, REST, WebSocket, Unified WebSocket, Embed).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, REST, WebSocket, Unified WebSocket, Embed

Source ↗

2026-11-17MaintenanceScheduled Maintenance - Full Exchange MaintenanceGeminiMay affect market data
Scheduled 21:00 to 02:00 UTC (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).
Details

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

Source ↗

2026-11-17InfoGlobal Derivatives moved from INTX to a Deribit-powered gatewayCoinbase Advanced Tradeeffective 2026-10-01
Advanced Trade international derivatives now trade on a Deribit-powered gateway on the Starbase platform. INTX perpetuals are no longer traded through the Advanced Trade API.
Details

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.

Source ↗

2026-11-17InfoNew endpoint: Get Institution Connection LimitBybit
A new REST endpoint, GET /v5/ins/connection-limit, returns JSON and SBE connection limits and current usage per dedicated endpoint.
Details

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.

Source ↗

2026-11-17Action neededOpen API Terms of Use revision (effective 12/10)Upbiteffective 2026-12-10
Upbit announced a revision to the Open API Terms of Use that takes effect on 12/10. The page shows only the headline, not the revised terms.
Details

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.

Source ↗

2026-11-17MaintenanceServer maintenance notice (completed)UpbitMay affect market data
Upbit posted a server maintenance notice that is marked as completed. The page gives no times or scope.
Details

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.

Source ↗

2026-11-17Action neededAPI path format and error handling review noticeUpbitMay affect market data
Upbit posted an important notice about reviewing API path formats and error handling. The page shows only the headline.
Details

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.

Source ↗

2026-11-17InfoUpbit SDK v1.1.0 expands WebSocket data type supportUpbit
Upbit released SDK v1.1.0 with broader WebSocket data type support.
Details

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.

Source ↗

2026-11-17InfoSelf-Match Prevention (SMP) default value appliedUpbit
Upbit announced a default value for Self-Match Prevention on orders.
Details

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.

Source ↗

2026-11-17InfoTechnical indicators now supported over WebSocketUpbit
Upbit added WebSocket support for technical indicators.
Details

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.

Source ↗

2026-11-17InfoNYSE Bonds - Addition to the List of Traded BondsNYSE XDP
NYSE Bonds added bonds to its list of traded bonds. The notice is tagged for Trading and Market Data.
Details

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.

Source ↗

2026-11-17InfoNYSE Bonds - Redemptions - Traded BondsNYSE XDP
NYSE Bonds announced redemptions of traded bonds.
Details

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.

Source ↗

2026-11-17InfoNYSE American Equities - Trading Resumption in AIRINYSE XDPMay affect market data
Trading resumed in AIRI on NYSE American Equities after a halt.
Details

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.

Source ↗

2026-11-17Action neededNew OPRA Dynamic Rebalance Symbol Distribution: confidence test Nov 21, activation Nov 23, 2026OPRA (consolidated US options)effective 2026-11-23Affects our handler
OPRA announced a confidence test on Saturday, November 21, 2026 and activation on Monday, November 23, 2026 for the new Dynamic Rebalance symbol distribution.
Details

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.

Source ↗

2026-11-17Action neededNYSE Arca: Extended Hours Trading testing - Nov 20 test, Nov 22 production pre-launchNYSE XDPMay affect market data
NYSE Arca announced testing for Extended Hours Trading, with a test on November 20 and a production pre-launch on November 22. The notice is tagged for Trading, Post Trade and Market Data.
Details

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.

Source ↗

2026-11-17InfoNYSE American - New Security Notification for Symbol ZOARNYSE XDPMay affect market data
NYSE American posted a notice about a new security with the symbol ZOAR. The text gives no further details.
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.

Source ↗

2026-11-16InfoNYSE Bonds - New Bond Listing - MS/33NYSE XDP
NYSE Bonds announced a new bond listing, MS/33.
Details

This is a new instrument on NYSE Bonds only. It has no effect on the XDP feeds we consume.

Our handler: NYSE Bonds listings are outside the XDP equities feeds.

Source ↗

2026-11-16InfoNYSE Bonds - New Bond Listing - LYG30C and LYG32ANYSE XDP
NYSE Bonds announced new listings for LYG30C and LYG32A.
Details

These are new bond instruments on NYSE Bonds. No effect on our equities feeds.

Our handler: NYSE Bonds listings are outside the XDP equities feeds.

Source ↗

2026-11-16InfoNYSE Bonds - Addition to the List of Traded BondsNYSE XDP
NYSE Bonds added bonds to its list of traded bonds.
Details

Only the notice title is available. It concerns NYSE Bonds, not our feeds. No action is needed.

Our handler: NYSE Bonds is not part of the XDP feeds we consume.

Source ↗

2026-11-16InfoNYSE Bonds - Traded Bonds - Change In Clearing StatusNYSE XDP
NYSE Bonds announced a change in clearing status for traded bonds.
Details

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.

Source ↗

2026-11-16InfoNYSE - Initial Pricing Regulatory Halt for Symbol TXRNYSE XDPMay affect market data
NYSE placed an initial pricing regulatory halt on symbol TXR.
Details

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.

Source ↗

2026-11-16InfoNYSE Bonds - New Bond Listing - EMR32ANYSE XDP
NYSE Bonds announced a new bond listing, EMR32A.
Details

This is a new instrument on NYSE Bonds only. No effect on our equities feeds.

Our handler: NYSE Bonds listings are outside the XDP equities feeds.

Source ↗

2026-11-13InfoSBE order entry and private data services launched in demoOKX
OKX launched SBE services for order entry and private order and fill updates in demo, with production expected in early December 2026. Existing REST and JSON WebSocket APIs are unaffected.
Details

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.

Source ↗

2026-11-13InfoCboe email system vendor issue closedCboe (BATS) Multicast PITCH
Cboe closed its alert on an email vendor disruption that delayed inbound email, which is now largely flowing with small delays. Other Cboe systems were operating normally.
Details

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.

Source ↗

2026-11-13InfoCboe email system issue resolved (final update)Cboe Futures Exchange (CFE) PITCH
Cboe closed its alert on the email vendor disruption. Email is flowing again with occasional multi-minute delays.
Details

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.

Source ↗

2026-11-13InfoCboe email system issue updateCboe Futures Exchange (CFE) PITCH
The email vendor's disruption was still being resolved, with delayed emails arriving and intermittent delays continuing.
Details

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.

Source ↗

2026-11-12MaintenanceKraken Website and API MaintenanceKrakenMay affect market data
Scheduled 08:01 to 08:16 UTC (Website, FIX, REST, WebSocket, Unified WebSocket, Embed).
Details

The scheduled maintenance will be postponed.

Our handler: Affects: Website, FIX, REST, WebSocket, Unified WebSocket, Embed

Source ↗

2026-11-12Action neededDerivatives WebSocket v1 deprecated; unavailable from 1 March 2027Krakeneffective 2027-03-01
The Derivatives WebSocket wss://futures.kraken.com/ws/v1 is deprecated and will stop working on 1 March 2027. New integrations should use the Unified WebSocket.
Details

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.

Source ↗

2026-11-12InfoCorporate actions query for stock-backed instrumentsOKX
A new public endpoint, GET Get corporate actions, returns corporate action events affecting stock-backed derivative instruments.
Details

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.

Source ↗

2026-11-12InfoTrading and matching engine migrated to AWS TokyoBybitMay affect market data
Bybit says it moved its trading and matching engine service to AWS Tokyo (apne1-az4) on 12 Nov 2026.
Details

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.

Source ↗

2026-11-12InfoNew user WebSocket hosts for fill and user_orders; warp hosts deprecatedKalshi Events Kalshi Perps
Lower-latency user-ws hosts now serve fill and user_orders, and the warp-ws and margin-warp-ws hosts are deprecated but still work.
Details

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.

Source ↗

2026-11-12InfoSubaccount-restricted keys can read margin funding history and balanceKalshi Events Kalshi Perps
Keys restricted to one subaccount can call GET /margin/funding_history and GET /margin/balance for that subaccount.
Details

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.

Source ↗

2026-11-12InfoFIX KalshiMD messages now carry MDExecIDKalshi Events Kalshi Perps
KalshiMD snapshots (35=W) and incremental updates (35=X) now include MDExecID<21046>.
Details

If your FIX engine validates custom tags, load the updated FIX dictionary.

Our handler: We consume market data over WebSocket, not FIX KalshiMD.

Source ↗

2026-11-12InfoFIX Security Status subscribe cost reduced to 1 tokenKalshi Events Kalshi Perps
FIX Security Status subscribe and unsubscribe requests (35=e) now cost 1 token instead of 10 from the shared Read bucket.
Details

No client change is required.

Our handler: This concerns the FIX API, which our handler does not use.

Source ↗

2026-11-12InfoCache-Control added to GET /markets/{ticker} and GET /events/{event_ticker}Kalshi Events Kalshi PerpsMay affect market data
These endpoints now send Cache-Control: public, max-age=5, so responses may come from a shared cache for up to 5 seconds.
Details

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.

Source ↗

2026-11-12InfoOn-request weather market endpoints addedKalshi Events Kalshi Perps
POST /weather_point_markets and GET /weather_point_markets/availability create and describe on-request weather markets (series starting KXRFQ).
Details

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.

Source ↗

2026-11-12InfoBalance endpoint documentation clarifiedKalshi Events Kalshi Perps
Docs for GET /portfolio/balance and GET /portfolio/subaccounts/balances were clarified; behaviour is unchanged.
Details

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.

Source ↗

2026-11-12InfoNew RFQ error codes on POST /communications/rfqsKalshi Events Kalshi Perps
Two RFQ refusals now return open_rfq_limit_exceeded and rfq_market_not_open instead of generic codes.
Details

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.

Source ↗

2026-11-12Infoinsufficient_shard_balance error details improvedKalshi Events Kalshi Perps
The error details now explain that API orders are not funded automatically and how to fund the exchange index.
Details

The error code and HTTP status are unchanged.

Our handler: This is an order-rejection error for trading, which we do not do.

Source ↗

2026-11-12InfoGET /api_keys now returns key_typeKalshi Events Kalshi Perps
Each supported API key now includes key_type (rsa or ed25519), including older keys.
Details

The field is omitted when the algorithm is unknown.

Our handler: Key management endpoint; not part of market data.

Source ↗

2026-11-12InfoNew ebattle_scores WebSocket channelKalshi Events Kalshi Perps
A new channel provides live eSoccer/eFootball and eBasketball scores, subscribed via subscribe_matches.
Details

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.

Source ↗

2026-11-12InfoMCP clients can read margin portfolio dataKalshi Events Kalshi Perps
Registered MCP clients can read margin balances, positions, orders, fills and risk with the read::mcp_portfolio OAuth grant.
Details

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.

Source ↗

2026-11-12InfoMCP clients can read settlementsKalshi Events Kalshi Perps
Registered MCP clients can read GET /portfolio/settlements with the read::mcp_portfolio OAuth grant.
Details

Archived settlements remain outside this endpoint.

Our handler: Account settlements endpoint; not public market data.

Source ↗

2026-11-12InfoMargin market_lifecycle_v2 now sends deactivated and activatedKalshi Events Kalshi PerpsMay affect market data
The margin market_lifecycle_v2 channel now also sends deactivated when a market's trading hours end and activated when they begin.
Details

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.

Source ↗

2026-11-12InfoCboe email system issue (vendor)Cboe Futures Exchange (CFE) PITCH
Cboe reported a vendor issue affecting inbound email receipt and directed users to phone the Trade Desk.
Details

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.

Source ↗

2026-11-12InfoCboe email system issue (vendor disruption)Cboe Futures Exchange (CFE) PITCH
Cboe reported a vendor issue affecting inbound email receipt and told customers to call the Trade Desk. Updates on Nov 13 said email was recovering, and the alert was closed with only minor delivery delays remaining.
Details

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.

Source ↗

2026-11-11MaintenanceDerivatives Platform MaintenanceKrakenMay affect market data
Scheduled 23:45 to 23:47 UTC (User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API

Source ↗

2026-11-11MaintenanceWebSocket, FIX + REST API MaintenanceKrakenMay affect market data
Scheduled 07:00 to 14:00 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-11-11MaintenanceOrder Entry System MaintenanceKrakenMay affect market data
Scheduled 09:00 to 10:00 UTC (Website, FIX, WebSocket, Kraken Pro App).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, WebSocket, Kraken Pro App

Source ↗

2026-11-11InfoMax open size direction-specific calculationOKX
In long/short position mode, maximum openable quantity calculations now differ by direction for SWAP and FUTURES.
Details

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.

Source ↗

2026-11-11InfoMargin market responses include minimum_quantityKalshi Events Kalshi PerpsMay affect market data
Margin market responses now include minimum_quantity, the minimum order quantity in contracts.
Details

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.

Source ↗

2026-11-10MaintenanceWebSocket, FIX + REST API MaintenanceKrakenMay affect market data
Scheduled 07:00 to 14:00 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-11-10MaintenanceOrder Entry System MaintenanceKrakenMay affect market data
Scheduled 10:00 to 11:00 UTC (Website, FIX, WebSocket, Kraken Pro App).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, WebSocket, Kraken Pro App

Source ↗

2026-11-10BreakingPublic open interest reported with 8-hour delayDeribitAffects our handler
Public open_interest on futures and options is now the value as of 8 hours ago, and real-time open interest is no longer available through the API.
Details

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.

Source ↗

2026-11-10Info24-hour volume split into realtime and delayed partsDeribitMay affect market data
The volume field now combines real-time volume with delayed Block RFQ volume, and new realtime/delayed breakdown fields were added.
Details

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.

Source ↗

2026-11-10InfoDelayed publication of large Block RFQ tradesDeribitMay affect market data
Qualifying large Block RFQ trades can be hidden from public trade feeds for up to 8 hours, then published out of sequence.
Details

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.

Source ↗

2026-11-10InfoChart volume excludes Block Trades and Block RFQ tradesDeribit
Block Trades and Block RFQ trades no longer add to volume in chart data.
Details

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.

Source ↗

2026-11-10Infoget_delivery_prices date filtersDeribit
public/get_delivery_prices accepts optional start_timestamp and end_timestamp filters.
Details

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.

Source ↗

2026-11-09MaintenanceWebSocket, FIX + REST API Maintenance.KrakenMay affect market data
Scheduled 08:00 to 14:00 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-11-09InfoAuto repay settings changes (spot margin)Bybit
Set Auto Repay Mode becomes a global switch when currency is omitted, and new get/set trade auto repay endpoints are added.
Details

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.

Source ↗

2026-11-06MaintenanceWebSocket, FIX + REST API Maintenance.KrakenMay affect market data
Scheduled 07:00 to 14:00 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-11-06InfoClassic account summary V3 response changed; sub-account mode field addedKuCoin
Get Account Summary Info (V3) now returns a new response structure. A new optional mode field was added to the Add Sub Account endpoints, and a UTA private funding fee settlement channel was added.
Details

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.

Source ↗

2026-11-05MaintenanceWebSocket, FIX + REST API MaintenanceKrakenMay affect market data
Scheduled 07:00 to 14:00 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-11-05InfoELP names retired in favor of RPI namesOKXeffective 2026-10-31
ELP names such as books-elp, ordType elp and elpMaker are no longer supported after 2026-10-31; use the RPI names.
Details

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.

Source ↗

2026-11-05InfoOn-request KXRFQ markets omitted from unscoped WebSocket subscriptionsKalshi Events Kalshi PerpsMay affect market data
Markets created on demand for RFQs (series starting KXRFQ) are left out of subscriptions that don't name markets.
Details

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.

Source ↗

2026-11-05InfoOn-request KXRFQ markets omitted from unscoped REST listingsKalshi Events Kalshi PerpsMay affect market data
GET /markets, GET /historical/markets and trade listings skip KXRFQ on-request markets unless the request names them.
Details

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.

Source ↗

2026-11-05InfoKalshi-cleared users need approved stocks application for Equities perpsKalshi Events Kalshi Perps
Orders or amends on Equities markets are rejected with stock_perps_application_required unless reduce-only.
Details

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.

Source ↗

2026-11-05InfoPerps price band now limits crossing the opposite sideKalshi Events Kalshi Perps
The Perps price band no longer limits resting distance and instead limits how far an order may cross the other side of the book.
Details

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.

Source ↗

2026-11-05Infonetting_enabled added to position responsesKalshi Events Kalshi Perps
Position endpoints now include netting_enabled for each position's event.
Details

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.

Source ↗

2026-11-05Action neededno_sub_title deprecated in favour of yes_sub_titleKalshi Events Kalshi PerpsMay affect market data
no_sub_title on REST markets and in WebSocket market lifecycle metadata is deprecated; it has equaled yes_sub_title since September 2024.
Details

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.

Source ↗

2026-11-05InfoPerps write budgets increased; order groups span marketsKalshi Events Kalshi Perps
Perps Write budgets double or triple as a single budget across all Perps markets, and Perps order groups can hold orders on any Perps market.
Details

exchange_index on Perps is deprecated.

Our handler: These concern order-writing budgets and order groups, which we do not use.

Source ↗

2026-11-05InfoExit trigger cancellations return status_reason market_deactivatedKalshi Events Kalshi Perps
Exit triggers canceled because their market was deactivated now return status_reason market_deactivated.
Details

Previously no status_reason was returned. The effective date is listed as TBD.

Our handler: Exit triggers are a trading feature.

Source ↗

2026-11-05InfoClearing Member API adds 6-decimal _fp dollar fieldsKalshi Events Kalshi Perps
Clearing Member margin endpoints add _fp dollar fields with 6 decimal places alongside _centicents fields.
Details

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.

Source ↗

2026-11-05InfoOptional update_interval_ms for orderbook_delta subscriptionsKalshi Events Kalshi PerpsAffects our handler
orderbook_delta subscriptions accept an optional update_interval_ms of 100 or 1000 to conflate deltas, with 0 or omission keeping real-time updates.
Details

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.

Source ↗

2026-11-05InfoFIX mass cancel allowed for subaccount-restricted keysKalshi Events Kalshi Perps
FIX sessions on single-subaccount keys can now send OrderMassCancelRequest (35=q).
Details

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.

Source ↗

2026-11-05Infomarket_closed error renamed market_inactiveKalshi Events Kalshi Perps
The market_closed order error is now market_inactive, and orders on a halted market return it too.
Details

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.

Source ↗

2026-11-04MaintenanceWebSocket, FIX + REST API MaintenanceKrakenMay affect market data
Scheduled 11:45 to 17:45 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-11-04InfoMark-price candle doc changes withdrawnBingX
BingX withdrew unconfirmed mark-price candle time descriptions, example changes and finality guidance, restoring the earlier text.
Details

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.

Source ↗

2026-11-04InfoMark-price candle response documentation correctedBingX
Docs now describe an array-of-objects response, string price types and the volume field. Endpoint behavior is unchanged.
Details

Documentation correction only. No action required.

Our handler: Swap candle REST documentation, unrelated to spot depth20 and trade channels.

Source ↗

2026-11-03InfoTokyo Dedicated Host has extra connection limit for JSON Market DataBybitMay affect market data
The JSON market data documentation notes that the Tokyo Dedicated Host gets an extra connection limit.
Details

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.

Source ↗

2026-11-03InfoEvent Contract quote and API key permission updatesBybit
Event Contract quote endpoints gain a cancelAfterMs parameter and a cancel-all endpoint, and API key endpoints add a ComplianceAppeal permission.
Details

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.

Source ↗

2026-11-03InfoUSDT-M markPriceKlines documentation correctedBingX
The docs for the USDT-M mark price kline endpoint were corrected (response shape, string price types, volume, openTime/closeTime). Endpoint behavior is unchanged.
Details

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.

Source ↗

2026-11-03InfopremiumIndex nextFundingTime documentation correctedBingX
nextFundingTime is documented as a UTC Unix millisecond timestamp of the next funding settlement, not a remaining duration. Fields and behavior are unchanged.
Details

Documentation clarification for /openApi/swap/v2/quote/premiumIndex. No action needed.

Our handler: Swap funding endpoint, not used by the spot handler.

Source ↗

2026-11-02MaintenanceFIX-API MaintenanceKrakenMay affect market data
Scheduled 15:00 to 16:30 UTC (FIX).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX

Source ↗

2026-11-02InfoUTA Get Orderbook becomes public with flexible depth and weighted rate limitKuCoinMay affect market data
The UTA REST Get Orderbook endpoint no longer requires authentication and accepts a wider range of depth values, including FULL. Its rate limit weight now depends on the requested depth.
Details

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.

Source ↗

2026-11-02InfoNew trading schedule endpoint for TradFi perpetualsBingX
Added /openApi/swap/v1/quote/tradingSchedule, which needs no API key. It returns 7 days of scheduled trading intervals and market status for non-crypto perpetual contracts.
Details

New public swap endpoint. No action needed for spot.

Our handler: USDT-M perpetual TradFi endpoint, outside the spot market feed.

Source ↗

2026-11-02InfoReduce-only clarification on swap order endpointBingX
Clarified that One-way Mode reduce-only closing orders are not rejected with 109415 solely because a contract is restricted from opening positions (status=25).
Details

Trading-only documentation clarification for /openApi/swap/v2/trade/order. No action needed.

Our handler: Swap trading endpoint; we do no trading.

Source ↗

2026-11-02InfoSwap fillHistory pagination docs correctedBingX
The unsupported lastFillId parameter was removed from the docs; use pageIndex and pageSize. Sending lastFillId returns error 100400.
Details

Account/trading endpoint /openApi/swap/v2/trade/fillHistory. No action needed.

Our handler: Private swap trade-history endpoint, outside public market data.

Source ↗

2026-10
2026-10-30MaintenanceKraken Pro US Futures MaintenanceKrakenMay affect market data
Scheduled 23:30 to 01:30 UTC (User Interface, Market Data, Bitnomial Exchange (BTNL), Order Placement).
Details

The scheduled maintenance has been completed.

Our handler: Affects: User Interface, Market Data, Bitnomial Exchange (BTNL), Order Placement

Source ↗

2026-10-30MaintenanceDerivatives Platform MaintenanceKrakenMay affect market data
Scheduled 08:00 to 08:15 UTC (User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API

Source ↗

2026-10-30MaintenanceKraken Website and API MaintenanceKrakenMay affect market data
Scheduled 08:00 to 08:15 UTC (Website, FIX, REST, WebSocket, Websocket API, Unified WebSocket, Embed, FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, REST, WebSocket, Websocket API, Unified WebSocket, Embed, FIX API

Source ↗

2026-10-30InfoUSDT-M incrDepth documentation correctedBingX
The swap {symbol}@incrDepth docs dropped the consecutive lastUpdateId +1 rule and revised the recovery guidance. They also note that lastUpdateId alone cannot reliably detect missing messages.
Details

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.

Source ↗

2026-10-29MaintenanceKraken Prime Scheduled MaintenanceKrakenMay affect market data
Scheduled 23:00 to 23:10 UTC (FIX, REST, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, REST, WebSocket

Source ↗

2026-10-29MaintenanceKraken Website and API MaintenanceKrakenMay affect market data
Scheduled 08:01 to 08:16 UTC (Website, FIX, REST, WebSocket, Unified WebSocket, Embed).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, REST, WebSocket, Unified WebSocket, Embed

Source ↗

2026-10-29MaintenanceDerivatives Platform MaintenanceKrakenMay affect market data
Scheduled 08:00 to 08:15 UTC (User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API

Source ↗

2026-10-29InfoNew endpoint: Get Corporate ActionsBybitMay affect market data
GET /v5/market/corporate-action returns current corporate actions such as stock splits and dividends.
Details

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.

Source ↗

2026-10-29InfoFixed-rate borrow endpoints addedBybit
New endpoints query fixed-rate borrow penalty interest and cancel eligible fixed-rate borrow orders.
Details

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.

Source ↗

2026-10-29InfoNew low-latency warp WebSocket hosts for fill and user_ordersKalshi Events Kalshi Perps
New warp-ws hosts deliver fill and user_orders updates with lower latency.
Details

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.

Source ↗

2026-10-29InfoMargin markets after final settlement report zero open interestKalshi Events Kalshi PerpsMay affect market data
After final settlement a margin market reports open interest of 0 and price equal to the final settlement price, with no added volume.
Details

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.

Source ↗

2026-10-29InfoGET /portfolio/credit_history addedKalshi Events Kalshi Perps
A new Predictions REST endpoint returns portfolio credit history.
Details

No client action needed.

Our handler: Account endpoint outside public market data.

Source ↗

2026-10-29InfoMargin WebSocket supports market_lifecycle_v2Kalshi Events Kalshi PerpsMay affect market data
The Margin WebSocket API now supports the market_lifecycle_v2 channel for market deactivation and activation.
Details

An optional channel; no change to existing subscriptions.

Our handler: A new margin channel that signals market activation state relevant to perp books.

Source ↗

2026-10-29InfoSubaccount-restricted keys can transfer between exchange indicesKalshi Events Kalshi Perps
Direct members can use subaccount-restricted keys for POST /portfolio/intra_exchange_instance_transfer.
Details

Moves funds within the subaccount between exchange indices.

Our handler: Funds transfer endpoint, not market data.

Source ↗

2026-10-29InfoRFQ batch messages added to communications channelKalshi Events Kalshi Perps
The communications WebSocket channel adds RFQ batch messages and rfq_batch_id fields across REST and FIX.
Details

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.

Source ↗

2026-10-29InfoMargin market responses carry halt_sourcesKalshi Events Kalshi PerpsMay affect market data
Margin market responses now include halt_sources, listing why a market is halted, empty when not halted.
Details

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.

Source ↗

2026-10-29InfoGet All Subaccount Balances accepts subaccount-restricted keysKalshi Events Kalshi Perps
The endpoint now accepts restricted keys and returns only the locked subaccount with per-exchange-index balances.
Details

No action for market data clients.

Our handler: Account balance endpoint.

Source ↗

2026-10-29InfoFIX market data requests accept entry type filtersKalshi Events Kalshi Perps
Optional NoMDEntryTypes<267> and MDEntryType<269> let FIX clients select bids, offers or trades.
Details

Omit them to receive all three.

Our handler: FIX market data requests; we use WebSocket.

Source ↗

2026-10-29InfoGET /portfolio/orders accepts up to 100 event tickersKalshi Events Kalshi Perps
The event_ticker filter now accepts up to 100 tickers, up from 10, and a filter on events with no markets returns no orders.
Details

Previously such a filter returned every order.

Our handler: Order listing is an account endpoint.

Source ↗

2026-10-29InfoPredictions orderbook_delta adds clock fieldKalshi Events Kalshi PerpsAffects our handler
Predictions orderbook_snapshot and orderbook_delta messages now include a clock field that is the same on every connection.
Details

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.

Source ↗

2026-10-29InfoDynamic Rebalance Industry Test #4 on Oct 31, 2026 (reminder, updated)OPRA (consolidated US options)effective 2026-10-31May affect market data
OPRA updated its reminder for Industry Test #4 of the Dynamic Rebalance symbol distribution on Saturday, October 31, 2026.
Details

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.

Source ↗

2026-10-28MaintenanceFIX-API maintenanceKrakenMay affect market data
Scheduled 22:00 to 22:30 UTC (FIX).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX

Source ↗

2026-10-28InfoSBE documented; schema 3:3 retired 11/9/2026Binance.USeffective 2026-11-09May affect market data
A Simple Binary Encoding section was added. SBE schema 3:5 is current; 3:2, 3:3 and 3:4 are deprecated, and 3:3 will be retired on 2026-11-09.
Details

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.

Source ↗

2026-10-27MaintenanceOrder Entry System MaintenanceKrakenMay affect market data
Scheduled 10:00 to 11:00 UTC (Website, FIX, WebSocket, Kraken Pro App).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, WebSocket, Kraken Pro App

Source ↗

2026-10-27InfoSpot REST: Algo Trading TWAP strategy endpoints addedKraken
New REST endpoints AddStrategy, CancelStrategy, GetOpenStrategies, QueryStrategies and GetClosedStrategies support TWAP strategies.
Details

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.

Source ↗

2026-10-27InfoNew bbo-rpi-tbt order book channelOKX
A new public WebSocket channel, bbo-rpi-tbt, pushes the best RPI bid and ask.
Details

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.

Source ↗

2026-10-26MaintenanceOrder Entry System MaintenanceKrakenMay affect market data
Scheduled 10:00 to 11:00 UTC (Website, FIX, Kraken App, WebSocket, Kraken Pro App).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Website, FIX, Kraken App, WebSocket, Kraken Pro App

Source ↗

2026-10-26MaintenanceScheduled maintenance - Trading services upgradeGeminiMay affect market data
Scheduled 03:00 to 03:15 UTC (Gemini ActiveTrader™, Gemini Mobile App: Uptime SLA 99.95%, Exchange Trading Engine, REST API, FIX API, Websockets API).
Details

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

Source ↗

2026-10-26InfoBZX Reg SHO circuit breaker messages not sent to CTA SIP; post mortemCboe (BATS) Multicast PITCHMay affect market data
On October 26 BZX failed to send Reg SHO short sale circuit breaker messages to the CTA SIP for Cboe-listed ETPs because of defective code in a weekend release. Cboe sent the messages manually and reverted the release after the close.
Details

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.

Source ↗

2026-10-26Action needed2027 testing schedule: failover to secondary data center and MWCB testingOPRA (consolidated US options)May affect market data
OPRA published its 2027 schedule for failover to the secondary data center and market-wide circuit breaker (MWCB) testing.
Details

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.

Source ↗

2026-10-26Info2027 OPRA testing blackout datesOPRA (consolidated US options)
OPRA published the dates in 2027 when testing will not be held.
Details

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.

Source ↗

2026-10-26InfoSelf-generated API keys (Ed25519/RSA)Binance.US
API keys can now be self-generated with Ed25519 or RSA key pairs and used for signing requests.
Details

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.

Source ↗

2026-10-24MaintenanceBCP/DR test: failover to Chicago disaster recovery siteCboe (BATS) Multicast PITCHMay affect market data
Cboe equities, options and futures exchanges stopped trading at 8 AM ET and failed over to the Chicago DR site as part of a BCP/DR test. Open orders were cancelled.
Details

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.

Source ↗

2026-10-24MaintenanceBCP/DR test: failover to Chicago disaster recovery siteCboe Futures Exchange (CFE) PITCHMay affect market data
At 8 AM ET Cboe Equities, Options and Futures Exchanges stopped trading in the primary site and began failing over to the DR site in Chicago as part of a test.
Details

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.

Source ↗

2026-10-23MaintenanceScheduled maintenance - FIX Order Entry services upgradeGeminiMay affect market data
Scheduled 02:00 to 02:15 UTC (FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX API

Source ↗

2026-10-23InfoAffiliate REST: payout-history expandedKraken
GET /affiliate/v1/payout-history now includes sub-affiliate commissions, approved retainers and approved remediation payouts.
Details

Affiliate reporting only; no market data impact.

Our handler: Affiliate REST endpoint, unrelated to book or trade feeds.

Source ↗

2026-10-23InfoNew error code 30035 for order limitMEXC
Error code 30035 was added, returned when the order limit is triggered.
Details

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.

Source ↗

2026-10-22MaintenanceScheduled maintenance - Trading services upgradeGeminiMay affect market data
Scheduled 03:00 to 03:15 UTC (Exchange Trading Engine).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Exchange Trading Engine

Source ↗

2026-10-22InfoDerivatives Maker Protection Phase 3 and behaviour changesKrakeneffective 2026-10-29
Maker Protection extends to 51 more Derivatives markets on 29 October 2026 at 08:00 UTC, and holds apply only to orders that would take liquidity.
Details

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.

Source ↗

2026-10-22BreakingWebSocket port 8443 discontinuationOKXeffective 2026-10-31Affects our handler
OKX will stop accepting WebSocket connections on port 8443 on 2026-10-31 for the public internet, and on 2026-11-16 for Colo. Port 443 already works on all affected domains.
Details

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.

Source ↗

2026-10-22InfoNew notice code 64010 for port 8443 retirementOKXAffects our handler
Connections on port 8443 receive a notice with error code 64010 after the handshake until the port is retired.
Details

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.

Source ↗

2026-10-22Infoclient_transfer_id returned on intra-exchange transfersKalshi Events Kalshi Perps
GET transfer endpoints optionally return the client_transfer_id sent when creating a transfer.
Details

No action needed.

Our handler: Funds transfer endpoints.

Source ↗

2026-10-22InfoMilestone details.status clarified as potentially staleKalshi Events Kalshi Perps
A milestone's details.status is maintained by a periodic job and may lag live game state.
Details

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.

Source ↗

2026-10-22InfoRedis authentication and TLS for WebSocket session and request limitsKalshi Events Kalshi PerpsMay affect market data
Added cache-specific Redis authentication and verified TLS for WebSocket session and request limits.
Details

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.

Source ↗

2026-10-22Infouser_orders timestamps truncated to millisecondsKalshi Events Kalshi Perps
user_order messages now truncate created_time, last_update_time and expiration_time to milliseconds without rounding.
Details

They remain RFC3339 strings and agree with the _ts_ms fields.

Our handler: Affects the user_orders channel, which we do not use.

Source ↗

2026-10-22InfoOpenAPI specifications correctedKalshi Events Kalshi Perps
The Predictions and Margin OpenAPI specs were corrected to match existing behavior.
Details

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.

Source ↗

2026-10-22InfoMargin funding averaged over clock-aligned barsKalshi Events Kalshi PerpsMay affect market data
Funding now averages the premium over clock-aligned bars of one second or longer, and invalid-premium handling applies per bar.
Details

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.

Source ↗

2026-10-22InfoFIX mass cancel by securityKalshi Events Kalshi Perps
OrderMassCancelRequest (35=q) accepts 530=1 with Symbol to cancel all resting orders in a market.
Details

The report answers with 531=1, and unknown tickers are rejected with 532=1.

Our handler: FIX order management.

Source ↗

2026-10-22InfoFIX SecurityStatus for margin corporate actionsKalshi Events Kalshi Perps
Margin KalshiNR and KalshiRT sessions receive SecurityStatus (35=f) on stock splits, final settlements and ticker changes.
Details

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.

Source ↗

2026-10-22InfoMargin corporate_actions WebSocket channelKalshi Events Kalshi PerpsMay affect market data
The public margin corporate_actions channel sends a corporate_actions_delta when a stock split, final settlement or ticker change is applied.
Details

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.

Source ↗

2026-10-22InfoGET /margin/corporate_actions endpointKalshi Events Kalshi PerpsMay affect market data
The endpoint returns scheduled notices and notices updated in the last seven days, with optional ticker and market_id filters.
Details

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.

Source ↗

2026-10-21MaintenanceKraken Prime and its WS/FIX APIsKrakenMay affect market data
Scheduled 23:00 to 23:10 UTC (FIX, WebSocket).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX, WebSocket

Source ↗

2026-10-21InfoClassic margin credit REST endpoints removedKuCoin
Classic REST margin lending endpoints (loan market, purchase, redeem) were removed from the docs.
Details

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.

Source ↗

2026-10-21InfoaccountStatus field documented on UID endpointBingX
The account UID endpoint now documents the accountStatus field (0 Normal, 1 Deregistered, 2 Locked).
Details

Account endpoint documentation only. No action needed.

Our handler: Account endpoint /openApi/account/v1/uid, outside public market data.

Source ↗

2026-10-21InfoPublic activity list endpoint addedBingX
Added /openApi/activity/v1/getPublicActivityList, which needs no key. The IP limit is 100 requests per 10 seconds.
Details

Promotional activity data, unrelated to market data feeds.

Our handler: Activity endpoint, not an order book or trade channel.

Source ↗

2026-10-20MaintenanceScheduled maintenance - FIX Order Entry services upgradeGeminiMay affect market data
Scheduled 03:00 to 04:00 UTC (FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX API

Source ↗

2026-10-20InfoReferral endpoints addedBybit
Four new referral endpoints cover commission records, campaign rewards, identity profile and invitations.
Details

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.

Source ↗

2026-10-20InfoPrivate activity list endpoint addedBingX
Added /openApi/activity/v1/getActivityList, which requires an API key and signature. It is limited to 100 requests per 10 seconds per IP.
Details

Account-side activity data. No action needed.

Our handler: Private activity endpoint, outside market data.

Source ↗

2026-10-20InfoChannel commission details endpoint addedBingX
Added the agent channel commission list endpoint, with pagination and filters. The limit is 10 requests per second per UID.
Details

Agent/partner endpoint. No action needed.

Our handler: Agent reward endpoint, unrelated to market data.

Source ↗

2026-10-20InfoSignal creation gets orderType parameterBingX
Create Signal now accepts an optional orderType (LIMIT by default, or MARKET) for take-profit and stop-loss orders.
Details

Trading-side change. No action needed.

Our handler: Social signal trading endpoint.

Source ↗

2026-10-20InfoNew trade ID field t on USDT-M @trade streamBingXMay affect market data
Each item in the USDT-M WebSocket {symbol}@trade data array now includes a t field, the matching trade ID, returned as a string.
Details

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.

Source ↗

2026-10-20InfoAPI key requirement removed from public market data docsBingXMay affect market data
The Spot, USDT-M and Coin-M public market data docs no longer require API key permission, and their examples omit keys and signatures. Timestamp requirements now reflect verified behavior.
Details

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.

Source ↗

2026-10-19MaintenanceScheduled maintenance - Trading Services UpgradeGeminiMay affect market data
Scheduled 00:30 to 01:00 UTC (Exchange Trading Engine).
Details

The scheduled maintenance has been completed.

Our handler: Affects: Exchange Trading Engine

Source ↗

2026-10-19InfoDerivatives Maker Protection hold cap raised to 500Kraken
The concurrent-hold cap per member rose from 250 to 500 requests.
Details

Requests past the cap are still refused with tooManyOrders. Trading-only.

Our handler: Derivatives trading limit, not market data.

Source ↗

2026-10-19InfoPost-only RFQ quote cancellations count toward penaltiesKalshi Events Kalshi Perps
If a maker's post-only order would cross the book at execution, the cancellation now counts toward quoting penalties.
Details

Repeated failures can temporarily rate limit new quotes.

Our handler: RFQ quoting is a trading feature.

Source ↗

2026-10-18MaintenanceScheduled maintenance - FIX Order Entry services upgradeGeminiMay affect market data
Scheduled 23:00 to 00:00 UTC (FIX API).
Details

The scheduled maintenance has been completed.

Our handler: Affects: FIX API

Source ↗

2026-10-15InfoBalance endpoint gets its own rate limit bucketKalshi Events Kalshi Perps
GET /portfolio/balance is metered separately: once per second for Basic and Advanced, five per second for higher tiers.
Details

Calls above the rate return 429, and balance calls no longer draw on the Read budget.

Our handler: Account balance endpoint.

Source ↗

2026-10-15InfoMCP read access and exclude_markets optionKalshi Events Kalshi Perps
Registered MCP clients can read portfolio data with the read::mcp_portfolio grant, and GET /events/{event_ticker} accepts exclude_markets=true.
Details

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.

Source ↗

2026-10-15InfoBatch margin orderbooks endpointKalshi Events Kalshi PerpsMay affect market data
GET /margin/markets/orderbooks returns orderbooks for up to 100 margin tickers in one request.
Details

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.

Source ↗

2026-10-15InfoClearer errors for multivariate collection creationKalshi Events Kalshi Perps
POST multivariate_event_collections now explains invalid_parameters rejections in the message field.
Details

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.

Source ↗

2026-10-15Infofunding_invalid_premium_handling added to margin marketsKalshi Events Kalshi PerpsMay affect market data
Margin market endpoints now include funding_invalid_premium_handling, set at creation.
Details

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.

Source ↗

2026-10-15InfoFunding deadband, cap and limit unit added to margin marketsKalshi Events Kalshi PerpsMay affect market data
Margin market endpoints now include funding_deadband, funding_cap and funding_limit_unit.
Details

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.

Source ↗

2026-10-15Infoclient_transfer_id for intra-exchange transfersKalshi Events Kalshi Perps
POST /portfolio/intra_exchange_instance_transfer accepts an optional UUID client_transfer_id for primary accounts.
Details

Reuse it only for identical retries. It is not supported for transfers involving numbered subaccounts.

Our handler: Funds transfer endpoint.

Source ↗

2026-10-15InfoMargin trades endpoint ticker filter optionalKalshi Events Kalshi PerpsMay affect market data
GET /margin/trades now accepts an optional ticker; omit it to get trades across all margin markets.
Details

Existing cursor pagination, timestamp filters and page limits still apply.

Our handler: Margin public trade data endpoint gains a broader query option.

Source ↗

2026-10-15Infobid_size_fp added to margin market responsesKalshi Events Kalshi PerpsMay affect market data
GET /margin/markets and GET /margin/markets/{ticker} now include bid_size_fp.
Details

An additive field; no client change is needed.

Our handler: The /margin/markets list we read gains a new field.

Source ↗

2026-10-15InfoNBBO calculation for Nasdaq switched to SIP dataCboe (BATS) Multicast PITCH
Effective 15:01:35 ET on October 15, the Cboe equities exchanges began using SIP data instead of Nasdaq direct feeds for Nasdaq NBBO calculations.
Details

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.

Source ↗

2026-10-14InfoNew endpoint: Get Instrument SummaryBybit
GET /v5/market/instrument-summary returns summary information and trading increments for linear and option instruments.
Details

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.

Source ↗

2026-10-13InfoNew execType and translog enum values for stock splitsBybit
execType adds ForwardSplitOpen and ReverseSplitOpen, and the uta-translog type adds FORWARD_SPLIT_OPEN and REVERSE_SPLIT_OPEN.
Details

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.

Source ↗

2026-10-13InfoNamed MMP group limit now per currency pairDeribit
The limit of 16 named MMP groups now applies per currency pair, and error 13038 includes currency_pair.
Details

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.

Source ↗

2026-10-09Infoli field added to TRADE_UPDATE order pushBingX
The account WebSocket TRADE_UPDATE push now includes li, the parent order ID for a take-profit or stop-loss order.
Details

Private account stream change. No action needed.

Our handler: Private order update stream, which we do not use.

Source ↗

2026-10-06InfoSpot REST: cursor pagination added to LedgersKraken
Ledgers now supports with_cursor and cursor, with a cursor.next response field.
Details

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.

Source ↗

2026-10-06InfoAlternative REST base endpoints api1 and api2Binance.USMay affect market data
https://api1.binance.us and https://api2.binance.us are now available, identical to api.binance.us in functionality and rate limits.
Details

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.

Source ↗

2026-10-05InfoAffiliate REST: cpa-progress and payout-history endpoints addedKraken
New GET /affiliate/v1/cpa-progress and GET /affiliate/v1/payout-history endpoints for affiliates.
Details

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.

Source ↗

2026-10-01InfoDerivatives Maker Protection Phase 2: 61 more marketsKrakeneffective 2026-10-08
Maker Protection extends to 61 further Derivatives markets on 8 October 2026.
Details

Read makerProtectionMillis on /instruments for the live set. Trading-only.

Our handler: Derivatives order handling, not Spot market data.

Source ↗

2026-09
2026-09-30InfoSpot REST: account_id, cursor pagination and field additions; some parameters deprecatedKraken
Many private Spot REST endpoints gain account_id, cursor pagination and new fields. The ofs parameter and some others are deprecated.
Details

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.

Source ↗

2026-09-30InfoInstruments channel push optimizationOKXMay affect market data
The Instruments channel now uses incremental pushes in some scenarios, sending only changed instruments.
Details

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.

Source ↗

2026-09-30BreakingUSD spot pairs migrated to USDC pairsOKXMay affect market data
Crypto-USD spot instruments have been delisted and the order books consolidated into the Crypto-USDC instruments.
Details

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.

Source ↗

2026-09-29InfoGlobal Liquidity Program API v2OKX
Three new authenticated REST endpoints under /api/v5/users/glp/v2/ cover GLP status and performance.
Details

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.

Source ↗

2026-09-29InfoGet Instruments Info adds tags field (linear and inverse)Bybit
Get Instruments Info has a new response field, tags, an array of symbol tags, for linear and inverse categories.
Details

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.

Source ↗

2026-09-22InfoOption base coins endpoint, delay liquidation status and Netherlands domain removalBybit
A new option base coins endpoint and an institutional delay liquidation endpoint were added, and the Netherlands domain was removed from integration guidance.
Details

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.

Source ↗

2026-09-21Action neededClassic Get Symbol / Get All Symbols add assetClass and subMarketType; marketType deprecatedKuCoinMay affect market data
The Classic symbol endpoints add assetClass and subMarketType response fields. The marketType field is marked deprecated.
Details

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.

Source ↗

2026-09-21InfoUTA fillPnl, brokerTag additions and new error code 116241KuCoin
UTA trade history, execution and order interfaces gain new fields, and a new position risk limit error code was added.
Details

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.

Source ↗

2026-09-17InfoAffiliate REST: daily-activity endpoint addedKraken
New GET /affiliate/v1/daily-activity for approved affiliates.
Details

Returns daily or ranged participant activity. No market data impact.

Our handler: Affiliate endpoint, unrelated to book or trade feeds.

Source ↗

2026-09-17InfolistenKey User Data Streams deprecated; sunset targeted Q4 2026Binance.US
The listenKey-based User Data Stream, including listenKey connections to wss://stream.binance.us:9443, will be retired on a date to be announced, targeted for Q4 2026.
Details

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.

Source ↗

2026-09-16Action neededExtension of OPRA trading hours effective Sep 21, 2026OPRA (consolidated US options)effective 2026-09-21Affects our handler
OPRA gave notice that its trading hours are extended, effective September 21, 2026.
Details

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.

Source ↗

2026-09-15InfoRPI maker minimum notional thresholdsOKX
RPI maker orders now have separate minimum notional amounts by product type, and orders below them are rejected with error 54051.
Details

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.

Source ↗

2026-09-15BreakingPosition updates omitted when order update has no tradeDeribit
user.changes channels no longer include positions unless a trade occurs.
Details

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.

Source ↗

2026-09-15InfoBasket index composition method postponedDeribit
The new public/get_basket_index_composition method will not be added in this release.
Details

No action needed.

Our handler: A method we do not use, and it was postponed.

Source ↗

2026-09-11InfoUniversal transfer supports new OTC account typeMEXC
The universal transfer endpoints now accept 'OTC' as a fromAccountType and toAccountType value, alongside SPOT and FUTURES.
Details

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.

Source ↗

2026-09-10InfoGet Instruments Info baseCoin=All for options; RPI taker IOC/FOKBybit
Get Instruments Info accepts baseCoin=All for option symbols, and rpiTakerAccess now works with Limit IOC/FOK orders.
Details

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.

Source ↗

2026-09-08Action neededSpot REST AssetPairs: fees and fees_maker deprecated and now emptyKrakenMay affect market data
The fees and fees_maker fields on the AssetPairs response now always return an empty array.
Details

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.

Source ↗

2026-09-08InfoDerivatives Maker Protection announced; live from 24 September 2026Krakeneffective 2026-09-24
Order actions that could take liquidity are held for a short fixed window on selected Derivatives markets.
Details

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.

Source ↗

2026-09-08Action neededRTH hardware upgrade and new trading session identifier: confidence test Sep 19, activation Sep 21, 2026OPRA (consolidated US options)effective 2026-09-21Affects our handler
OPRA's Regular Trading Hours system hardware upgrade and new trading session identifier go live Monday, September 21, 2026, with a confidence test on Saturday, September 19.
Details

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.

Source ↗

2026-09-07InfoBrazil and Argentina internal accounts: use main hosts, no x-site-id headerBybit
For internal accounts in Brazil and Argentina, REST should use api.bybit.com and WebSocket stream.bybit.com without the x-site-id header.
Details

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.

Source ↗

2026-09-05InfoPosition query returns 109500 when service is unavailableBingX
Query Position Data now returns error 109500 when the position service is temporarily down, instead of code 0 with empty data.
Details

Account endpoint behavior change. No action needed.

Our handler: Private swap positions endpoint.

Source ↗

2026-09-04InfoNew error code 110188 (system busy)KuCoin
Error code 110188 was added for when the system is busy and too many requests are being made.
Details

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.

Source ↗

2026-09-02InfoEvent Contract OpenAPI launchedBybit
Bybit launched an Event Contract OpenAPI with market and trade endpoints and WebSocket streams.
Details

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.

Source ↗

2026-09-02InfoBZX degraded network link affecting order entry sessions resolvedCboe (BATS) Multicast PITCH
BZX saw sporadic TCP retransmissions on order entry sessions caused by a degraded link between switches. Cboe shut the link and traffic moved to a redundant path.
Details

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.

Source ↗

2026-09-01InfoMaintenance and incident advisories added across Spot API protocolsKrakenMay affect market data
The WS v2 status channel gains upcoming_maintenance and emergency objects. WS v1, REST (SystemStatus, MaintenanceSchedule) and FIX get equivalents.
Details

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.

Source ↗

2026-09-01InfoFutures instruments gain PendingOpen status; fee group merge; isFixApi fieldBybit
Futures instrument status adds PendingOpen, fee groups G2-G5 and USDC merge into Altcoin, and Get API Key Information adds isFixApi.
Details

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.

Source ↗

2026-09-01BreakingRemoval of buyer/seller order ID fields from <symbol>@tradeBinance.USeffective 2026-08-31Affects our handler
The buyer order ID and seller order ID fields were removed from the <symbol>@trade stream payload as part of the 8/31/2026 upgrade.
Details

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.

Source ↗

2026-09-01Action neededLocal order book guide updated; snapshot limit up to 5000Binance.USeffective 2026-08-31Affects our handler
The documented steps for managing a local order book were updated, with depth snapshots now referencing up to 5000 levels per side and clearer buffering and sync steps.
Details

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.

Source ↗

2026-09-01Info/api/v1/* endpoints retiredBinance.USeffective 2026-08-31May affect market data
All /api/v1/* REST endpoints, including depth and trades, have been retired in favor of /api/v3/*.
Details

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.

Source ↗

2026-09-01InfoNew symbolStatus parameter on GET /api/v3/depthBinance.USeffective 2026-08-31May affect market data
GET /api/v3/depth gains an optional symbolStatus parameter (TRADING, HALT, BREAK); a mismatch for a single symbol returns error -1220.
Details

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.

Source ↗

2026-08
2026-08-31InfoIntegration methods added for Hong Kong, Argentina and Brazil usersBybit
New REST and WebSocket integration guidance was added for Hong Kong (08-31), Argentina (08-28) and Brazil (08-09) users.
Details

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.

Source ↗

2026-08-31InfoFunding rate history docs clarifiedBingX
Funding rate history returns only completed settlement records, with no current or estimated rate and no nextFundingTime.
Details

Documentation clarification for the swap endpoint. No action needed.

Our handler: Swap funding rate REST endpoint.

Source ↗

2026-08-28InfoNew fee fields rpiMakerRebate and rpiMakerFeeRateBybit
Get Fee Group Structure adds rpiMakerRebate and Get Fee Rate adds rpiMakerFeeRate.
Details

These are additive fee fields on authenticated endpoints.

Our handler: Fee endpoints are account related.

Source ↗

2026-08-28InfoDual-Currency place order docs correctedBingX
The required permission is now Spot Trading, several parameters are marked required, and the quote source is documented.
Details

Wealth product trading documentation. No action needed.

Our handler: Wealth trading endpoint.

Source ↗

2026-08-27InfoInstruments info adds fullName, marketRegion, underlyingTickerBybitMay affect market data
Get Instruments Info and Get Account Instruments Info add fullName, marketRegion and underlyingTicker to tell apart symbols for the same stock on different venues.
Details

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.

Source ↗

2026-08-27BreakingUTA API V2 upgrade: URLs and many field changesKuCoin
All UTA API endpoints were moved to V2 URLs, with many renamed or changed request and response fields compared with V1.
Details

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.

Source ↗

2026-08-26InfoNew endpoint: Get Delta hedge currenciesOKX
A new endpoint maps tokenized assets to their underlying currencies for hedging.
Details

This is informational and requires no action.

Our handler: It concerns hedging and account use, not the books or trades channels.

Source ↗

2026-08-26InfoVST environment removed from Coin-M docsBingX
The Coin-M REST and WebSocket docs no longer list the VST environment. Only PROD is supported.
Details

Applies to Coin-M only. No action needed.

Our handler: Coin-M futures environments, not spot.

Source ↗

2026-08-25InfoOption batch order size reduced to 5Bybit
Batch place, amend and cancel for category=option now allow a batch size of 5 on REST, WebSocket and SBE order entry.
Details

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.

Source ↗

2026-08-25InfoNBBO calculation for NYSE symbols S-Z switched to SIP dataCboe (BATS) Multicast PITCH
Effective 13:05:31 ET on August 25, the Cboe equities exchanges began using SIP data for NYSE NBBO calculations in symbol range S-Z.
Details

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.

Source ↗

2026-08-24InfoSwap Place order parameter rules clarifiedBingX
Clarified the closePosition, quantity, reduceOnly and positionId requirements for the swap Place order endpoint.
Details

Trading documentation only. No action needed.

Our handler: Swap trading endpoint.

Source ↗

2026-08-24InfoSwap Test Order parameter rules clarifiedBingX
The Test Order docs now match the Place order rules for closePosition, quantity, reduceOnly and positionId.
Details

Trading documentation only. No action needed.

Our handler: Swap trading test endpoint.

Source ↗

2026-08-24InfoDocumentation added for GET /api/v3/apiKeyInfoMEXC
MEXC documented the endpoint that queries API key information, including permissions, IP whitelist and remaining validity.
Details

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.

Source ↗

2026-08-21InfoForm-urlencoded body signing rules addedBingX
Signature docs now say that signatures for application/x-www-form-urlencoded bodies must be computed over the final URL-encoded string actually sent.
Details

Affects authenticated requests only. Our feeds need no signing.

Our handler: Signed REST requests; our WebSocket market channels use no auth.

Source ↗

2026-08-20InfoDerivatives REST: off-book risk preferences and assignment program parametersKrakeneffective 2026-08-27
New /rfq-assignment/max-leverage endpoints and minimum profitability parameters for assignment participants, available from 27 August 2026, 07:00 UTC.
Details

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.

Source ↗

2026-08-20InfoWebSocket Orders channel push behavior adjustmentOKX
For post-only and RPI orders, the state:live event is pushed only after the order enters the book, and is omitted when the order is canceled.
Details

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.

Source ↗

2026-08-20InfoexecType and translog enum changes; Broker Earning FIAT_CONVERTBybit
execType removes CorporateAction and adds ForwardSplitSettle, ReverseSplitSettle and Dividend. Broker earning adds FIAT_CONVERT.
Details

These are private execution and broker data changes.

Our handler: They affect private execution and broker endpoints, not public orderbook data.

Source ↗

2026-08-20InfoUTA fill size sign fix and Exchange Broker markup fee endpointsKuCoin
UTA trade history and execution data now return positive quantities for ADL, liquidation and settlement fills. Two Exchange Broker markup fee endpoints were added.
Details

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.

Source ↗

2026-08-19InfoSpot REST: ListWalletAccounts added; account_id on Balance and LedgersKraken
New ListWalletAccounts endpoint, and Balance and Ledgers accept an account_id parameter.
Details

Account-level endpoints only.

Our handler: Private Spot REST account endpoints, not used by our handler.

Source ↗

2026-08-19InfoDynamic Rebalance Industry Test #1 on Aug 29, 2026OPRA (consolidated US options)effective 2026-08-29May affect market data
OPRA offered an industry test of the new Dynamic Rebalance symbol distribution on Saturday, August 29, 2026.
Details

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.

Source ↗

2026-08-18InfoRPI maker minimum notional amountOKX
RPI maker orders are subject to a minimum notional amount, and orders below it are rejected with error 54051.
Details

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.

Source ↗

2026-08-18InfoAsset Overview response restructuredBybit
UnifiedTradingAccount in Asset Overview now returns a categories breakdown (crypto, stocks) instead of a flat coinDetail list.
Details

This is a response shape change on an account endpoint.

Our handler: Asset Overview is an account endpoint that we do not use.

Source ↗

2026-08-18InfoUTA REST rate limits increasedKuCoin
The UTA resource pool rate limits were raised for all VIP levels.
Details

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.

Source ↗

2026-08-18BreakingEstimated liquidation ratio fields removedDeribit
estimated_liquidation_ratio and estimated_liquidation_ratio_map were removed from portfolio and account summary objects.
Details

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.

Source ↗

2026-08-18InfoSpot trading routed to Coinbase ExchangeDeribit
Selected spot instruments are now matched on Coinbase Exchange, with limited order types and some market data endpoints unsupported.
Details

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.

Source ↗

2026-08-18InfoOPRA GTH confidence test on Aug 22, 2026OPRA (consolidated US options)effective 2026-08-22May affect market data
OPRA issued a notice and test plan for a GTH confidence test on Saturday, August 22, 2026.
Details

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.

Source ↗

2026-08-14InfoexchangeInfo adds conceptPlateIds and conceptPlates fieldsMEXCMay affect market data
GET /api/v3/exchangeInfo responses now document the new fields conceptPlateIds and conceptPlates.
Details

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.

Source ↗

2026-08-14InfoTrade stream [email protected] adds version fieldMEXCAffects our handler
The aggregated trade WebSocket stream documentation now includes a response field named version, with an updated sample payload.
Details

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.

Source ↗

2026-08-12InfoUTA trade history and position list field changes; sub-account API ipWhitelist ruleKuCoin
Small response changes to UTA trade history and position list. The Classic sub-account API endpoints now require ipWhitelist when the Transfer (Withdraw) permission is granted.
Details

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.

Source ↗

2026-08-11InfoRPI maker spacing and visibility rule updateOKX
The RPI maker spacing rule now references only the first visible opposite-side RPI, and hidden RPI are excluded.
Details

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.

Source ↗

2026-08-11InfoFull Depth Orderbook now supports FuturesBybit
The Get Full Depth Orderbook REST endpoint and the Full Orderbook WebSocket channel now support Futures.
Details

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.

Source ↗

2026-08-11InfoEstimated liquidation price deprecation for segregated_smDeribit
estimated_liquidation_price will no longer be returned for segregated_sm accounts.
Details

Affects private/get_position and private/get_positions. Still available through Position Builder.

Our handler: Private position endpoints are not used.

Source ↗

2026-08-11InfoUnaggregated .raw market data aggregated at 1 msDeribitMay affect market data
All .raw subscriptions are now aggregated on a 1 millisecond basis.
Details

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.

Source ↗

2026-08-11InfoStarbase identifiers on orders and tradesDeribit
New starbase order and trade ID fields were added to order, user trade, combo leg and transaction log objects.
Details

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.

Source ↗

2026-08-11InfoNew instrument fields product_group and index_idDeribit
get_instrument and get_instruments now return product_group and index_id.
Details

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.

Source ↗

2026-08-10InfoCoin-M trade order moved to v2 pathBingX
Coin-M Trade Order is upgraded to the v2 path. positionSide is required and the order fields are returned under data.order.
Details

Trading endpoint. No action needed for market data.

Our handler: Coin-M trading endpoint.

Source ↗

2026-08-07InfoCrypto loan inventory endpoints and strategyType parameterBybit
New available-inventory endpoints were added for fixed-term and flexible crypto loans, and strategyType was added to fixed-term borrow orders.
Details

These are account and lending changes.

Our handler: They are crypto loan endpoints unrelated to market data.

Source ↗

2026-08-07InfoPosition history upgraded to v2 with USDC supportBingX
Query Position History moves to the v2 path. It uses startTime and endTime, returns realizedProfit, and supports USDC symbols such as BTC-USDC.
Details

Account endpoint. No action needed.

Our handler: Private swap account endpoint.

Source ↗

2026-08-07InfoallFillOrders supports USDCBingX
Query historical transaction orders now supports currency=USDC and USDC symbols. The response currency may be USDT or USDC.
Details

Account endpoint. No action needed.

Our handler: Private swap order-history endpoint.

Source ↗

2026-08-07InfoallOrders supports USDCBingX
Query Order history now supports currency=USDC and USDC symbols, with a maximum range of 7 days.
Details

Account endpoint. No action needed.

Our handler: Private swap order endpoint.

Source ↗

2026-08-07InfofillHistory supports USDCBingX
Query historical transaction details now supports currency=USDC and USDC symbols. commissionAsset may be USDT or USDC.
Details

Account endpoint. No action needed.

Our handler: Private swap fill endpoint.

Source ↗

2026-08-07InfoPositions endpoint gets currency filterBingX
Query position data now accepts a currency parameter (USDT or USDC). If omitted, positions in all settlement currencies are returned.
Details

Account endpoint. No action needed.

Our handler: Private swap positions endpoint.

Source ↗

2026-08-07InfoIncome endpoint gets currency parameterBingX
The profit and loss fund flow endpoint now supports a currency parameter for USDT or USDC, defaulting to USDT.
Details

Account endpoint. No action needed.

Our handler: Private swap income endpoint.

Source ↗

2026-08-06Action neededHistorical market data maximum query range reducedOKX
The maximum query range on Get historical market data was reduced from 20 to 10.
Details

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.

Source ↗

2026-08-06BreakingsmpGroup type changed from integer to string; position mode and TradFi updatesBybit
smpGroup changes from integer to string in Get Order History, Get Open Orders and the WS Order stream, and smpType is added to Get Trade Behaviour Config.
Details

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.

Source ↗

2026-08-05InfoPosition history pageIndex docs clarifiedBingX
pageIndex for Query Position History starts at 0 and defaults to 0 when omitted.
Details

Documentation only. No action needed.

Our handler: Private swap account endpoint.

Source ↗

2026-08-04InfoSelf Match Prevention rules and UTA Pro upgrade windowBybit
SMP becomes mandatory for Kazakhstan derivatives, spot smpType None is set to CancelMaker for TUR, KAZ and GEO, and UTA Pro upgrades are blocked 07:55-08:05 UTC daily.
Details

These affect trading and account settings only.

Our handler: They are trading and account rules, not public market data.

Source ↗

2026-08-03InfoHidden and iceberg orders discontinued in Classic REST; new UTA endpointsKuCoin
Classic order endpoints reject requests with hidden, iceberg or visibleSize parameters. Four UTA REST endpoints were added.
Details

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.

Source ↗

2026-07
2026-07-30InfoRPI permission model and RFQ updatesBybit
RPI permission moves from account-level to symbol-level, and RFQ endpoints gain hedge legs and a new Get RFQ Details endpoint.
Details

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.

Source ↗

2026-07-30Action neededHigher request weights, including GET /api/v3/depthBinance.USeffective 2026-08-31Affects our handler
Depth weight is now 5 (limit 1-100), 25 (101-500), 50 (501-1000) and 250 (1001-5000), with other limit and weight changes including REQUEST_WEIGHT raised to 6,000 per minute.
Details

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.

Source ↗

2026-07-30Action neededWebSocket ping every 20s, pong timeout 1 minuteBinance.USeffective 2026-08-31Affects our handler
The WebSocket server now sends a ping frame every 20 seconds and disconnects if no pong arrives within 1 minute.
Details

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.

Source ↗

2026-07-30Action neededNew serverShutdown eventBinance.USeffective 2026-08-31Affects our handler
A serverShutdown event is sent as a JSON text frame when the server is about to shut down.
Details

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.

Source ↗

2026-07-30InfoexchangeInfo permissions moved to permissionSetsBinance.USeffective 2026-08-31May affect market data
Symbol permission data in GET /api/v3/exchangeInfo moves from permissions, which becomes empty, to permissionSets, with an optional showPermissionSets parameter.
Details

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.

Source ↗

2026-07-30InfoTrading-related changes: filters, expiryReason, executionReport, WS API weightBinance.USeffective 2026-08-31
New order filters, expiryReason in order responses, executionReport changes, a new myFilters endpoint, and WebSocket API connection weight of 2 were announced.
Details

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.

Source ↗

2026-07-29InfoSpot Recent Trades List moved to v2 quote pathBingXMay affect market data
Recent Trades List is upgraded to /openApi/spot/v2/quote/trades, and the timestamp and recvWindow parameters are removed.
Details

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.

Source ↗

2026-07-29InfoSpot Kline endpoint moved to v2 quote pathBingX
Kline/Candlestick Data is upgraded to /openApi/spot/v2/quote/klines, and the order of all eight array fields is documented.
Details

REST change. No impact on our WebSocket depth and trade channels.

Our handler: Spot kline REST endpoint, which we do not consume.

Source ↗

2026-07-29InfoSpot 24hr ticker moved to v2 quote pathBingX
24hr Ticker Price Change Statistics is upgraded to /openApi/spot/v2/quote/ticker, with priceChange, best bid/ask and time fields aligned to the actual response.
Details

REST change. No action needed for our WebSocket handler.

Our handler: Spot ticker REST endpoint, which we do not consume.

Source ↗

2026-07-29InfoSpot order book aggregation moved to v2 quote pathBingXMay affect market data
Order Book aggregation is upgraded to /openApi/spot/v2/quote/depth. The depth request parameter is renamed limit and type is now required.
Details

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.

Source ↗

2026-07-29InfoSpot Symbol Price Ticker moved to v2 quote pathBingX
Symbol Price Ticker is upgraded to /openApi/spot/v2/quote/price, symbol becomes optional, and data is now documented as an array.
Details

REST change. No impact on our WebSocket channels.

Our handler: Spot price REST endpoint, which we do not consume.

Source ↗

2026-07-29InfoSpot Order Book Ticker moved to v2 quote pathBingX
Symbol Order Book Ticker is upgraded to /openApi/spot/v2/quote/bookTicker. Quantity fields are now bidQty and askQty, and a time field is added.
Details

REST change. No impact on our @depth20 and @trade channels.

Our handler: Spot best bid/ask REST endpoint, which we do not consume.

Source ↗

2026-07-29InfoSpot Historical K-line moved to v2 quote pathBingX
Historical K-line is upgraded to /openApi/spot/v2/quote/historicalKlines, with the result limit and eight array fields documented.
Details

REST change. No action needed.

Our handler: Spot historical kline REST endpoint, which we do not consume.

Source ↗

2026-07-29InfoSpot Historical Trades moved to v2 quote pathBingX
Historical Trades is upgraded to /openApi/spot/v2/quote/historicalTrades, with field definitions and types aligned to the actual response.
Details

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.

Source ↗

2026-07-28InfoSpot-X Launchpool, Puzzle and Token Splash endpoints addedBybit
New endpoints were added for Spot-X Launchpool, Puzzle and Token Splash projects and user activity.
Details

These are product and account endpoints. No action is needed.

Our handler: They are launch-event product endpoints unrelated to the orderbook feed.

Source ↗

2026-07-27InfoNew endpoint: Get Referral CodeBybit
A new endpoint returns the referral codes and registration links owned by the current user.
Details

Sub-accounts return the master account's codes. Account only.

Our handler: It is a referral account endpoint.

Source ↗

2026-07-27InfoHardware upgrade industry tests on Aug 8, 2026 (OPRA and OPRA-GTH)OPRA (consolidated US options)effective 2026-08-08May affect market data
OPRA reminded participants of industry tests for the OPRA and OPRA-GTH system hardware upgrades on Saturday, August 8, 2026.
Details

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.

Source ↗

2026-07-24InfoOpen API domains updated for Japan region usersBybitMay affect market data
Integration guidance was updated with new Open API domains for Japan region users (following additions on 2026-07-06).
Details

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.

Source ↗

2026-07-23InfoNew execType value CorporateActionBybit
A new execType value, CorporateAction, covers stock splits and reverse splits.
Details

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.

Source ↗

2026-07-21InfoFast Order Response: options supported, XML template v2Bybit
The Fast Order Response now supports options, and its XML template is upgraded to v2 with four added response fields.
Details

This applies to the order entry feed only.

Our handler: Fast Order Response is a trading-side stream, not public orderbook data.

Source ↗

2026-07-21InfoNew private/get_currencies and Starbase fields on Trade and OrderDeribit
Added private/get_currencies and Starbase ID and timestamp fields on trade and order objects.
Details

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.

Source ↗

2026-07-21InfoSIAC support of 2026 SIFMA industry-wide business continuity testingOPRA (consolidated US options)May affect market data
SIAC announced its support for the 2026 SIFMA industry-wide business continuity testing.
Details

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.

Source ↗

2026-07-21InfoNew error code 157005 for withdrawal protectionMEXC
Error code 157005 was added: withdrawal is currently locked by withdrawal protection.
Details

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.

Source ↗

2026-07-13InfoNew endpoint: add deposit addressLBank
LBank added POST /v2/supplement/add_deposit_address.do, which creates a new multi-chain deposit address for a user.
Details

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.

Source ↗

2026-01
2026-01-07Action neededDynamic Rebalance Symbol Distribution: industry tests and go-live Nov 23, 2026OPRA (consolidated US options)effective 2026-11-23Affects our handler
OPRA set industry tests and a go-live date of November 23, 2026 for the new Dynamic Rebalance symbol distribution.
Details

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.

Source ↗