
Kalshi API Changelog 2026: What Changed, What to Fix
The Kalshi API changelog lives at docs.kalshi.com/changelog, with an RSS feed at /changelog/rss.xml, and it is the only place Kalshi announces breaking changes to the REST, WebSocket and FIX APIs. It is also long: 259 dated entries since June 2025, mixed across the Predictions and Margin exchanges. This page is the short version for people who run bots against the Predictions API, rebuilt from the source on November 16, 2026 and checked against the live API.
Key Takeaway: Three things need action before or around November 19, 2026: stop reading
expiration_time(uselatest_expiration_time), move fill and order streams from the deprecatedwarp-wshosts touser-ws, and stop branching onmarket_closed(nowmarket_inactive) ortoo_many_requestsfor RFQ refusals. Everything else in the last three months is additive.
We refresh this page once a month. The tracker below is ordered by what can break your code, not by date.
How to read the Kalshi changelog
Each entry carries two kinds of tags: the surface (REST, WebSocket, FIX) and the exchange (Predictions, Margin). If you trade event contracts, filter to Predictions and ignore Margin-only entries, which cover the perps exchange described in our Kalshi margin trading post.
One quirk is worth knowing. Entries are filed under the date they take effect, not the date they were written. The six entries headed November 19, 2026 were posted between November 11 and 13 according to the RSS pubDate field. So on November 16 the changelog already described changes that were a few days away, and the live API still behaved the old way. We confirmed that below for expiration_time. Read a future-dated entry as an announcement.
Breaking changes and deprecations
| Effective | Change | What to do |
|---|---|---|
| Nov 19 | expiration_time removed from market objects, including markets nested in events | Read latest_expiration_time, which has always held the same value |
| Nov 19 | expected_expiration_time is capped at latest_expiration_time | Re-check any code that sorts or filters by expected expiry on multi-strike events |
| Nov 12 | warp-ws and margin-warp-ws hosts deprecated, replaced by user-ws hosts | Change the host for fill and user_orders subscriptions |
| Nov 12 | POST /communications/rfqs returns open_rfq_limit_exceeded (429) and rfq_market_not_open (400) | Handle the new codes, and do not retry the first one as rate limiting |
| Nov 5 | market_closed error is now market_inactive, also returned for halted markets | Update any string match on the old error code |
| Nov 5 | no_sub_title deprecated, equal to yes_sub_title on every market since September 2024 | Use yes_sub_title; the field is still returned |
| Oct 29 | GET /portfolio/orders with an event_ticker filter for an event that has no markets now returns no orders | Previously it returned every order; check any code that relied on that |
| Oct 15 | GET /portfolio/balance has its own rate limit bucket (1 per second on Basic and Advanced, 5 per second above) | Stop polling balance; react to fills instead |
| Oct 22 | user_orders timestamps truncated to milliseconds without rounding | Parse RFC 3339 strings, or use the _ts_ms fields |
| Sep 10 | available_on_brokers removed from event responses | Delete the field from your models |
Two details deserve a longer look.
The expiration_time removal has not happened yet. When we called GET /events/KXFEDDECISION-26DEC and GET /markets/KXFEDDECISION-26DEC-C26 on November 16, 2026, expiration_time and latest_expiration_time both came back as 2027-03-10T19:01:00Z. The expected_expiration_time was 2026-12-09T19:05:00Z, the actual FOMC decision date. If your bot treats expiration_time as the date a market settles, it was already wrong for this kind of event: the latest expiration is the outer bound, while the expected expiration is when Kalshi expects the outcome. Use both fields on purpose.
The error code changes bite quietly. A bot that retries on too_many_requests will now retry an RFQ refusal that cannot succeed until open RFQs close. Kalshi says so explicitly: open_rfq_limit_exceeded is not request-rate limiting. The same logic applies to the new weather_point_market_limit_exceeded and concert_cancellation_market_limit_exceeded codes, which are 429 responses that are not about request rate. Branch on the error code, never on the status alone. Our rate limits guide covers the backoff code for the real token-bucket 429s.
Rate limit headers and caching
The entry dated November 19 adds four headers to REST responses: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and X-RateLimit-Cost. They describe the bucket your request was charged to, so a client can stop guessing its remaining budget. Two limits to remember: 429 responses carry the headers but no Retry-After, and publicly cacheable responses carry none of them.
That second point matches what we measured. A public GET /markets?limit=1&status=open returned Cache-Control: public, max-age=15 and no rate limit headers on November 16, 2026. GET /events/{ticker} and GET /markets/{ticker} both returned Cache-Control: public, max-age=5, which is the November 12 change. If you poll a single market once a second, you are mostly reading a shared cache, so the price can be up to five seconds old. For live prices, subscribe to the ticker channel as the changelog advises, and see the WebSocket guide.
Expert insight: Most “my bot got a stale price” bugs after November 12 are cache hits, not Kalshi outages. If a REST poll disagrees with the order book by a few cents, check the
Cache-Controlheader before you check your logic.
WebSocket changes since September
The WebSocket surface got the most additions, none of them breaking:
sending_ts_msis now on every WebSocket message (October 1), so you can measure transport latency separately from your own processing.clockonorderbook_delta(October 29): unlikeseq,clockis identical on every connection, which lets you reconcile a market across redundant connections.update_interval_msonorderbook_delta(November 5): set100or1000to receive one netted delta per changed price level per window. Your own order updates and snapshots bypass the interval. A repeated subscribe must use the same interval or you get error code 11.permessage-deflatecompression is supported when your client offers it in the handshake (September 24). Omit it to stay uncompressed.cfbenchmarks_value_5hz(September 3) streams CF Benchmarks index values at up to five updates per second for BRTI and four other indices, useful for the crypto contracts we cover in the 15-minute strategy post.ebattle_scores(November 12): live eSoccer and eBasketball scores, public to authenticated users for a limited period only.- User hosts:
wss://user-ws.kalshi.com/trade-api/ws/v2servesfillanduser_orders, with more per-user channels promised. The demo equivalent iswss://user-ws.demo.kalshi.co/trade-api/ws/v2. Subscribing to any other channel on a dedicated host returns error code 8.
New endpoints worth knowing
settlement_statusonGET /portfolio/positions(October 1):unsettled(default),settledorall. Usesettledfor positions that have settled but have not yet moved intoGET /historical/positions.- Batch filters (October 8 and 29):
GET /portfolio/fillsaccepts up to 100 comma-separated tickers, andGET /portfolio/ordersaccepts up to 100event_tickervalues, up from 10. exclude_markets=trueonGET /events/{event_ticker}(October 15) for metadata-only reads. We confirmed it on November 16: the response forKXFEDDECISION-26DECreturned an empty markets list. Page through outcomes withGET /markets?event_ticker=...&cursor=....GET /incentive_schedules(November 19 entry, already live) lists recurring liquidity incentive schedules and needs no authentication. It returned HTTP 200 on November 16, including a schedule for the 2028 House winner market.- On-request markets.
POST /weather_point_marketscreates or returns a weather market for a location, time window and threshold, and you trade it through an RFQ. Its/availabilityendpoint is public and returned HTTP 200. The concert cancellation endpoints followed the same pattern, but their availability call returned"enabled": falseon November 16, matching the changelog’s “not live yet”. These KXRFQ markets are hidden from unscopedGET /marketslistings (November 5), so a market scanner will not see them unless you filter by series or ticker. - Ed25519 keys (September 24): accepted on REST, WebSocket and FIX with the same headers as RSA. See the API key guide.
GET /api_keysnow returnskey_type. - Rate limits: Premier, Paragon, Prime and Prestige read and write limits rose 20% on September 24.
Watch the changelog with 25 lines of Python
This script polls the RSS feed, keeps only the surfaces you use, and prints entries it has not shown before. We ran it on November 16, 2026 against the live feed: the first run printed 11 Predictions entries (REST and WebSocket), the second run printed none.
import xml.etree.ElementTree as ET
import requests
FEED = "https://docs.kalshi.com/changelog/rss.xml"
WANT = {"REST", "WebSocket"} # surfaces you use
EXCHANGE = "Predictions" # or "Margin"
seen_file = "kalshi_changelog_seen.txt"
try:
seen = set(open(seen_file).read().split())
except FileNotFoundError:
seen = set()
root = ET.fromstring(requests.get(FEED, timeout=15).content)
new = []
for item in root.iter("item"):
guid = item.findtext("guid")
tags = {c.text for c in item.findall("category")}
if guid in seen or EXCHANGE not in tags or not (tags & WANT):
continue
new.append((item.findtext("pubDate")[5:16], sorted(tags), item.findtext("title")))
seen.add(guid)
for day, tags, title in new:
print(day, "|", "/".join(tags), "|", title)
print(f"{len(new)} new entries")
open(seen_file, "w").write("\n".join(seen))
Run it from cron once a day and pipe the output to your alerting channel. The feed only holds the latest 15 entries, so do not leave it unchecked for months. For older history, read the full page. If you run bots around the clock, the Hermes cron setup shows one way to schedule it.
What we are watching next
Three open items we will check on the next update: whether expiration_time actually disappears from live responses after November 19, when the concert markets go live, and what Kalshi adds to the user-ws hosts beyond fills and orders. The Kalshi API reference lists the endpoints themselves, and the payout calculator handles the fee maths that the API does not.
Fees remain a cost: Kalshi’s taker fee is round up(0.07 x C x P x (1 - P)), capped at 1.75 cents per contract, and the maker fee depends on the series. Source for all changelog entries: docs.kalshi.com/changelog. Checked November 16, 2026.
For a bot that already handles signing, backoff and the host switch, the Kalshi bot kit is the paid shortcut, and the free cheat sheet covers the endpoints and fee formulas on one page. If you do not have an account yet, you can open a Kalshi account and start in demo first.
EdgeOutcome may earn a commission if you open a Kalshi account through the link above. It does not change what you pay.
18+. Prediction markets involve real financial risk. Availability depends on your country and US state.
Frequently Asked Questions
Where is the official Kalshi API changelog?
At docs.kalshi.com/changelog, with an RSS feed at docs.kalshi.com/changelog/rss.xml. Every entry is tagged by surface (REST, WebSocket, FIX) and by exchange (Predictions, Margin), and the page can be filtered by those tags. On November 16, 2026 the page listed 259 dated entries going back to June 12, 2025, while the RSS feed carried only the 15 most recent.
How do I get notified about Kalshi API breaking changes?
Subscribe to the RSS feed at docs.kalshi.com/changelog/rss.xml, which Kalshi itself recommends for staying ahead of breaking changes. Kalshi also asks for feedback in the #dev channel of its Discord. The short Python watcher on this page polls the feed, filters by REST or WebSocket and prints only entries you have not seen before.
Was the Kalshi expiration_time field removed from market objects?
It is scheduled for removal. The changelog entry dated November 19, 2026 says the deprecated expiration_time field is removed from market objects, including markets nested in events, and that latest_expiration_time carries the same value. When we called GET /events/KXFEDDECISION-26DEC on November 16, 2026 both fields were still returned with identical values, so switch to latest_expiration_time now. Order expiration_time is a different field and is unchanged.
Does Kalshi send rate limit headers on API responses?
Yes, since the entry dated November 19, 2026. REST responses describe the bucket a request was charged to with X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (seconds until the bucket is full) and X-RateLimit-Cost. 429 responses carry them but not Retry-After, and publicly cacheable responses such as most market data carry none. On November 16, 2026 a public GET /markets response showed Cache-Control: public, max-age=15 and no X-RateLimit headers, which matches the documentation.
Which Kalshi WebSocket host should I use for fills and order updates?
The user hosts: wss://user-ws.kalshi.com/trade-api/ws/v2 in production and wss://user-ws.demo.kalshi.co/trade-api/ws/v2 in demo. They serve the fill and user_orders channels. The earlier warp-ws hosts are deprecated but keep working with the same channels for now. Both host families answered an unauthenticated upgrade request with HTTP 401 on November 16, 2026, which is the expected response without signed headers.