Event and market monitoring
Mit Kalshi-Endpunkten verwandelst du event and market monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Collect Kalshi events, markets, series, recent trades, order books, exchange schedule, and historical market candlesticks as normalized JSON for dashboards and research. Not investment advice or real-time trading data.
Extract Kalshi events, markets, series, trades, order books, and historical market data as structured JSON from credential-free public exchange data.
Endpunkt-Familien
6
Dokumentierte Parameter
84
Beispiele
21
Live-Katalog-Snapshot
Aktive Endpunkte
21
Methoden
GET
Pflichtparameter
32
Schema-Referenzen
21
{
"platform": "Kalshi",
"endpoint": "kalshi-events",
"method": "GET",
"path": "/kalshi/events",
"auth": "apiKey"
}Verwandte Use Cases
Use Cases
Extract Kalshi events, markets, series, trades, order books, and historical market data as structured JSON from credential-free public exchange data.
Mit Kalshi-Endpunkten verwandelst du event and market monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Kalshi-Endpunkten verwandelst du order book and trade research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Kalshi-Endpunkten verwandelst du historical market data collection in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Kalshi-Endpunktkatalog — 21 Endpunkte, 84 dokumentierte Request-Parameter und 21 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
21 documented Kalshi endpoints, grouped into 8 request families — Historical, Event and Market, plus 5 more.
84 request parameters are documented across those Kalshi endpoints, 32 of them required — the full input contract is public before you write any integration code.
21 of the 21 Kalshi endpoints ship a recorded example response, and 21 carry a documented response schema — you can code against the real JSON before the first request.
Kalshi endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
21 hosted MCP tools back the Kalshi endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/kalshi/historical/markets
/kalshi/event/{event_ticker}
/kalshi/market/{ticker}
/kalshi/markets
/kalshi/events
/kalshi/exchange/status
Ausgewählte Endpunkte
/kalshi/eventsLists Kalshi events, up to `limit` rows (default 25, max 200), continued with `cursor`. Filter by `series_ticker`, `category`, `status` (`open`, `closed` or `settled`), `min_close_ts` and `min_updated_ts`. `with_nested_markets` adds each event's markets. Each event has its ticker, title, category and strike period. A `cursor` is returned when more rows exist.
Hinweise zur Response
- `data.cursor` is present when Kalshi returns a next-page cursor. - Invalid `status`, `min_close_ts`, or `min_updated_ts` values return invalid-parameter errors before upstream IO.
MCP-Tool kalshi_events
/kalshi/event/{event_ticker}Returns one Kalshi event by `event_ticker` (such as `KXELONMARS-99`) together with its markets. The event has its series ticker, title, subtitle, category, strike period and mutually-exclusive flag; each market has prices, bid and ask, volume, open interest, status and rules. An unknown ticker returns a not-found error.
Hinweise zur Response
- Invalid or empty event tickers return invalid-parameter errors before upstream IO. - Missing upstream events return not-found errors.
MCP-Tool kalshi_event
/kalshi/marketsLists Kalshi markets, up to `limit` rows (default 25, max 200), continued with `cursor`. Filter by `event_ticker`, `series_ticker`, `ticker`, or `status` (`unopened`, `open`, `closed` or `settled`). Each market has its title, status, prices, bid and ask, volume, open interest and rules text. A returned status can read `active` even though the filter does not accept it.
Hinweise zur Response
- Invalid `status` values return invalid-parameter errors before upstream IO. - The upstream response status field can contain exchange lifecycle values such as `active`; the query `status` filter still only accepts `unopened`, `open`, `closed`, and `settled`. - This endpoint is not investment advice or real-time trading data.
MCP-Tool kalshi_markets
/kalshi/market/{ticker}Returns one Kalshi market by `ticker` (such as `KXELONMARS-99`). The response has the title, subtitle, event ticker, status, result, open, close and expiration times, last and previous price, yes and no bid and ask, volume, 24-hour volume, open interest, liquidity and rules text. An unknown ticker returns a not-found error.
Hinweise zur Response
- Invalid or empty market tickers return invalid-parameter errors before upstream IO. - Missing upstream markets return not-found errors. - This endpoint is not investment advice or real-time trading data.
MCP-Tool kalshi_market
/kalshi/market/{ticker}/orderbookReturns the order book for one Kalshi market by `ticker`: bid levels for the `yes` side and the `no` side, each with `price` and `size`. Kalshi publishes bids only, so ask levels are not listed. The response also carries a `raw_unit_hint` for the price unit.
Hinweise zur Response
- Uses Kalshi's unauthenticated market orderbook JSON. - Kalshi returns bid levels for yes and no sides; no ask levels are returned directly.
MCP-Tool kalshi_market_orderbook
/kalshi/tradesLists recent Kalshi trades, up to `limit` rows (default 25, max 200), continued with `cursor`. Filter by market `ticker` and by created time with `min_ts` and `max_ts` (Unix seconds, at most 366 days apart). Each trade has its id, count, yes and no price, taker side and created time.
Hinweise zur Response
- Trade prices are normalized from dollar fields such as `yes_price_dollars` and `no_price_dollars`. - `min_ts` must be before `max_ts` when both are provided, and timestamp ranges are capped at 366 days. - This endpoint is not investment advice or real-time trading data.
MCP-Tool kalshi_trades
Verwandte APIs
Prediction Markets
Collect Polymarket event and market detail, token prices, order books, midpoints, spreads, price history, tags, sports, leaderboards, and trade activity as normalized JSON for dashboards, research, and agent-native workflows. Not investment advice or real-time trading data.
Prediction Markets
Collect Metaculus questions, community forecasts and forecast history, question metadata, options, and comment feeds as normalized JSON for research and tracking. Not investment, forecasting, or decision advice.
Prediction Markets
Read the public navigation and reference material from DraftKings Predictions without confusing it for a market feed. The endpoints return category links, settlement-source references, and a region/status map; they do not return quotes, trades, balances, or trade-slip state.
So scrapst du Kalshi
Kalshi is a regulated event exchange whose public market data is credential-free but split across live and historical services. Crawlora's 21 Kalshi endpoints return events, markets, series, order books, trades, schedules, and historical candlesticks as normalized JSON. Research data, not investment advice or a trading connection.
List events with a status of open, closed, or settled — optionally with nested markets — or list series and open one by its ticker.
Markets are addressed by ticker: market detail, order book, and trades all take it, and market lists filter by event or series ticker.
Market and event history take start and end timestamps with a period interval, and batch variants take several market tickers at once.
Exchange status and schedule tell you whether the exchange is open, and the historical-cutoff endpoint tells you how far back the historical services reach.
On 2026-10-30 /kalshi/event/KXELONMARS-99 returned one market, its history for the window 1704067200 to 1704153600 (one day, period_interval 1440) returned candlesticks for that market, and its metadata listed 17 settlement sources.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Kalshi-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Kalshi ab:
Compare public event forecasts across Crawlora Polymarket, Kalshi, and Metaculus tools. Use for a matched-question consensus brief or dated forecast…
npx skills add github.com/Crawlora-org/crawlora-skills --skill forecast-consensus-comparisonResearch prediction-market odds, order books, price history, and public market-rule context from Polymarket, Kalshi, Metaculus, and DraftKings…
npx skills add github.com/Crawlora-org/crawlora-skills --skill prediction-markets-researchFAQ
Kalshi publishes credential-free public market-data JSON, which is what these endpoints read. Crawlora is not affiliated with Kalshi and this is not a trading connection — it is read-only data behind one key with a consistent response shape.
The live set covers currently listed events, markets, order books, and trades. The historical set covers settled and archived markets, and the historical-cutoff endpoint tells you the boundary between them so you know which to query for a given date.
Market history takes a ticker with start and end timestamps and a period interval. The batch variant takes a list of market tickers, so you can chart every market in an event at once.
No. These endpoints are read-only market data for dashboards and research. Crawlora is not a broker or an investment adviser, and nothing here is investment advice.
Yes. Kalshi's official API assigns every new account its default Basic tier — 200 read / 100 write tokens per second — and reserves the higher Advanced through Prime tiers for accounts that clear a trailing 30-day trading-volume threshold or get manually upgraded by Kalshi. A research or dashboard use case with no trading volume has no self-serve path to a higher tier; these endpoints read the same public data behind one Crawlora key instead.