/kalshi/markets/history

POST /api/kalshi/markets/history

Price: 10 credits

Get OHLC price-history candlesticks for a prediction-market contract over a time window

How to use it

Get historical OHLC candlesticks for a single prediction-market contract over a time window. Provide the series_ticker and market ticker, a start_ts/end_ts Unix-second window, and a period_interval (1m, 1h or 1d). Each candle carries end_period_at plus the open/high/low/close/mean trade price, traded volume, open interest, and the yes-bid and yes-ask OHLC sub-series.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• series_ticker string required — Series ticker the market belongs to (examples: "KXBTCD", "KXHIGHNY"; minLength: 1)
• ticker string required — Market ticker of the tradeable Yes/No contract (examples: "KXBTCD-26JUN1604-T74799.99"; minLength: 1)
• start_ts integer required — Window start as a Unix timestamp in seconds (min: 0)
• end_ts integer required — Window end as a Unix timestamp in seconds (min: 0)
• period_interval integer required — Candle interval in minutes: 1 (1m), 60 (1h), or 1440 (1d) (one of: 1, 60, 1440)

Response

• @type string (default: "KalshiCandlestick")
• end_period_at integer required
• open number nullable
• high number nullable
• low number nullable
• close number nullable
• mean number nullable
• previous number nullable
• volume integer nullable
• open_interest integer nullable
• yes_bid object nullable
  • @type string (default: "KalshiCandlestickOHLC")
  • open number nullable
  • high number nullable
  • low number nullable
  • close number nullable
• yes_ask object nullable
  • @type string (default: "KalshiCandlestickOHLC")
  • open number nullable
  • high number nullable
  • low number nullable
  • close number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Market not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.