The Kalshi live order-book feed is available across a bounded, changing cohort of markets — dozens at a time, not every open Kalshi market. Discover the served set through signed
GET /stream/kalshi/partner/coverage; all_open_markets is false. Check GET /stream/capabilities for your organisation’s entitled state before connecting.Order-book feed
The Kalshi order-book feed serves a bounded, changing cohort of markets over the shared authenticated order-book format: a snapshot then sequenced full-book replacements, both sides quoted as exact decimal strings. It is not every open Kalshi market — discover the current set through signedGET /stream/kalshi/partner/coverage, which returns the served scope, the ready / pending / retired lists and all_open_markets: false. Short-duration contracts roll over; re-read coverage to find replacement tickers.
Checking the live state
GET /stream/capabilities is the contract for what this venue serves, per organisation, right
now. It separates three facts that are easy to read as one:
For Kalshi today,
implemented and upstream_registered are true; connect once your
organisation’s entitled state is true. Availability is still per market — inspect the stream
status and wait for a snapshot before using a book.
Access
Kalshi is a read-only data entitlement, granted separately from the trading venues. Holding Polymarket or Predict.fun access does not include it. Market Data connections need a credential withstream.read on an eligible paid plan — see authentication and
API credits.
Native Kalshi market data provides current books, catalogue metadata, public trades and native candles over REST. Historical Kalshi order-book depth (captured history) is available separately through REST with a Data credential and Kalshi data grant: point-in-time book reconstruction over content-addressed generations, from September 2026 where coverage exists, with every gap disclosed. Continuous historical depth — the full change stream over an arbitrary range, and backfill further into the past — is being delivered in stages; a bounded Parquet export can be scoped with the team in the meantime. Captured history is not the live book feed.
All Kalshi endpoints
Every Kalshi surface in one place. Two credentials: the Market Data credential (stream.read) for the live feed and its discovery, and the Data API credential (analytics.read + Kalshi data grant) for the REST surfaces. Each row links to the page documenting it in full.
Live feed — WebSocket · Order-book feed
Connect with the Market Data credential. Basewss://partner-api.bravadotrade.com.
Live feed — discovery & health (signed GET)
Native REST pass-through · Native market data
Data API credential. Basehttps://partner-api.bravadotrade.com/market-data/v1/native.
Computed · Liquidity
Data API credential. Basehttps://partner-api.bravadotrade.com/market-data/v1/computed.
Historical order-book depth · Captured history
Data API credential. Basehttps://partner-api.bravadotrade.com/market-data/v1.
Product coverage
Tax statements, PMWAS reconciliation and entity rollups are Polymarket-only.
Venue details
Related
- Supported prediction markets, coverage by product across every venue
- Multi-venue order books, the shared message format
- Polymarket overview, the fully supported reference implementation