These endpoints return raw Kalshi data directly from the Kalshi API without normalization. Use them when you need platform-specific fields that the unified API strips out.Documentation Index
Fetch the complete documentation index at: https://docs.arbiterapi.com/llms.txt
Use this file to discover all available pages before exploring further.
When to use native endpoints
| Use case | Endpoint |
|---|---|
| Cross-platform dashboards, analytics | Unified API (/v1/markets) |
| Kalshi trading bots | Native API (/v1/kalshi/markets) |
| Event-level grouping by Kalshi tickers | Native API (/v1/kalshi/markets) |
Platform-specific fields
| Field | Type | Description |
|---|---|---|
ticker | string | Kalshi market ticker (e.g., KXBTC-26MAR28-100000) |
event_ticker | string | Parent event ticker |
series_ticker | string | Series ticker |
yes_bid / no_bid | integer | Best bid in cents (1-99) |
yes_ask / no_ask | integer | Best ask in cents (1-99) |
yes_bid_dollars / no_bid_dollars | float | Best bid in dollars |
volume | integer | Total contracts traded |
open_interest | integer | Open contracts |
ID mapping
Every unified market withplatform: "kalshi" has an ID formatted as kal_{ticker}. Strip the kal_ prefix to get the ticker for native endpoints.