Event and market monitoring
Use Kalshi endpoints to turn event and market monitoring into repeatable API requests with documented inputs and JSON responses.
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.
Endpoint families
6
Documented params
84
Examples
21
Live catalog snapshot
Active endpoints
21
Methods
GET
Required params
32
Schema refs
21
{
"platform": "Kalshi",
"endpoint": "kalshi-events",
"method": "GET",
"path": "/kalshi/events",
"auth": "apiKey"
}Related 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.
Use Kalshi endpoints to turn event and market monitoring into repeatable API requests with documented inputs and JSON responses.
Use Kalshi endpoints to turn order book and trade research into repeatable API requests with documented inputs and JSON responses.
Use Kalshi endpoints to turn historical market data collection into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/kalshi/historical/markets
/kalshi/event/{event_ticker}
/kalshi/market/{ticker}
/kalshi/markets
/kalshi/events
/kalshi/exchange/status
Featured endpoints
/kalshi/eventsReturns normalized Kalshi event rows from credential-free public market-data JSON.
/kalshi/event/{event_ticker}Returns one normalized Kalshi event row and its normalized markets from credential-free public market-data JSON.
/kalshi/marketsReturns normalized Kalshi market rows from credential-free public market-data JSON. The `status` enum accepts `unopened`, `open`, `closed`, and `settled`.
/kalshi/market/{ticker}Returns one normalized Kalshi market row from credential-free public market-data JSON.
/kalshi/market/{ticker}/orderbookReturns normalized yes/no bid levels for one Kalshi market ticker from public orderbook JSON.
/kalshi/tradesReturns normalized recent Kalshi market trades from credential-free public market-data JSON.
Related 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.