Perpetual futures: US stocks, indices, crypto, metals, energy. A snapshot per market with plain bid/ask levels, then deltas that change one level by a signed number of contracts.
Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.
Open live bookswss://external-api-margin-ws.kalshi.com/trade-api/ws/v2/marginhttps://external-api.kalshi.com/trade-api/v2/margin/markets (market list with contract size, reference and mark prices, funding cap)KXBTCPERP{"id":1,"cmd":"subscribe","params":{"channels":["orderbook_delta"],"market_tickers":["KXBTCPERP","KXETHPERP",...]}}
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.
Once an account hits its limit, a request that would create a new market returns the existing error code flight_disruption_market_limit_exceeded, and the message says it is the account's limit. Requests that return an existing market (created: false) do not count toward the limit and are still answered at the limit. No error codes are added or changed. This is an on-request market creation endpoint; a market data client that only reads order books and the public market list needs to do nothing.
Our handler: POST /flight_disruption_markets is an account-level market creation endpoint, not the orderbook_delta channel or the public market list we use.
The 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.
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.
Swaps wallets are created by Kalshi and are separate from the primary account and numbered subaccounts. Clients that switch exhaustively on subaccount_type should accept the new value. This concerns balance, position and risk rows, which are account data; our handler only consumes public order book data, so no action is needed.
Our handler: The subaccount_type field appears on margin balance, position and risk rows (account data), not on the public orderbook_delta channel or market list.
Per the fragment, once a market's close_time (or the show's start) is 24 hours away or less, the request returns an error code with a reason instead of the market being returned. The market stays open until close_time, positions are unaffected, the market endpoint still returns it, and settlement is unchanged. The text is incomplete, so the exact endpoint is unclear. Market-list consumers should verify that markets near close still appear as expected.
Our handler: The fragment says the market list endpoint still returns such markets, but the wording is incomplete and may relate to order creation only.
Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.