Event and market monitoring
Kalshiエンドポイントを使えば、「Event and market monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
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.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
84
サンプル数
21
ライブカタログスナップショット
稼働エンドポイント
21
メソッド
GET
必須パラメータ
32
スキーマ参照
21
{
"platform": "Kalshi",
"endpoint": "kalshi-events",
"method": "GET",
"path": "/kalshi/events",
"auth": "apiKey"
}ユースケース
Extract Kalshi events, markets, series, trades, order books, and historical market data as structured JSON from credential-free public exchange data.
Kalshiエンドポイントを使えば、「Event and market monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Kalshiエンドポイントを使えば、「Order book and trade research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Kalshiエンドポイントを使えば、「Historical market data collection」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のKalshiエンドポイントカタログから取得しています（エンドポイント21件、ドキュメント化されたリクエストパラメータ84個、公開レスポンススキーマ21件）。DocsとPlaygroundが参照しているカタログと同じものです。
Kalshiのエンドポイントは21件、8つのリクエストファミリーに分類されています（Historical、Event、Marketほか5件）。
これらのKalshiエンドポイントには84個のリクエストパラメータがドキュメント化されており、うち32個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
21件のKalshiエンドポイントのうち21件が実際のサンプルレスポンスを、21件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Kalshiのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、500、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Kalshiのエンドポイントは21個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/kalshi/historical/markets
/kalshi/event/{event_ticker}
/kalshi/market/{ticker}
/kalshi/markets
/kalshi/events
/kalshi/exchange/status
主要エンドポイント
/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.
レスポンスに関する注記
- `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ツール 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.
レスポンスに関する注記
- Invalid or empty event tickers return invalid-parameter errors before upstream IO. - Missing upstream events return not-found errors.
MCPツール 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.
レスポンスに関する注記
- 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ツール 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.
レスポンスに関する注記
- 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ツール 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.
レスポンスに関する注記
- Uses Kalshi's unauthenticated market orderbook JSON. - Kalshi returns bid levels for yes and no sides; no ask levels are returned directly.
MCPツール 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.
レスポンスに関する注記
- 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ツール kalshi_trades
関連API
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.
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.
FAQ
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.