Feeds / Kalshi (live)

Kalshi — event contracts

Event contracts (yes/no): daily BTC, ETH, SOL, XRP; gold and silver; S&P 500 and Nasdaq-100. A snapshot per market, then deltas that change one price level by a signed number of contracts.

Live in productionWebSocketFull book

Live now

-
books live
-
messages / s
-
level changes / s
-
KB / s

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 books

How we connect

Market
Event contracts (yes/no): daily BTC, ETH, SOL, XRP; gold and silver; S&P 500 and Nasdaq-100
WebSocket
wss://external-api-ws.kalshi.com/trade-api/ws/v2
Channels
orderbook_delta — one subscription carries every market
Update model
A snapshot per market, then deltas that change one price level by a signed number of contracts. Our book is the YES contract: yes bids are bids, no bids become asks at $1 − p.
Snapshot (REST)
https://external-api.kalshi.com/trade-api/v2/markets?status=open&series_ticker={SERIES} (market list; books come over the WebSocket)
Sequencing
seq on the subscription must be exactly the previous + 1 on every message that carries one; deltas for a market are dropped until it has a snapshot.
On a gap
All markets are marked unsynced and the handler reconnects (new signed handshake) and resubscribes for fresh snapshots. Every 10 minutes we also request fresh snapshots of every market (update_subscription get_snapshot), so each capture file starts with full books.
Depth
Full book
Authentication
Signed WebSocket handshake: key id, millisecond timestamp and an Ed25519 or RSA-PSS signature, signed fresh for each connection. The REST market list is public.
Heartbeat
Kalshi sends WebSocket pings; we answer with pongs. Reconnect after 30 s without data.
Symbol format
KXBTCD-26NOV1618-T65399.99

Subscribe message

{"id":1,"cmd":"subscribe","params":{"channels":["orderbook_delta"],"market_tickers":["KXBTCD-26NOV1618-T65399.99",...]}}

What our handler takes care of

Instruments

loading...

Upcoming and recent changes

2026-11-26InfoNew endpoints for on-request flight disruption markets
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-21InfoPer-account 24-hour limit on creating flight disruption markets
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-20InfoEndpoint now accepts up to 100 comma-separated market tickersMay 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-20InfoRFQs on request-created markets always obscure creator ID
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-20InfoNew 'swaps' value for subaccount_type on margin balance, position and risk rows
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 hoursMay 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 ↗

Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed

Official documentation

Kalshi — WebSocket orderbook updates ↗docs.kalshi.comKalshi — WebSocket connection ↗docs.kalshi.comKalshi — connection keep-alive ↗docs.kalshi.comKalshi — orderbook responses (yes/no bids) ↗docs.kalshi.comKalshi — get markets (REST) ↗docs.kalshi.comKalshi — API keys and request signing ↗docs.kalshi.comKalshi — rate limits ↗docs.kalshi.comKalshi — API changelog ↗docs.kalshi.com

Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.