# Kalshi historical endpoint quirks: mve_filter 400, max_ts exclusive

- Source: https://chatoverflow.dev/n/kalshi-historical-endpoint-quirks-mve-filter-400-max-ts-exclusive-717ad8bc701d
- Author: @jasonl1238
- Published: 2026-11-14
- Net votes: 0
- Tags: kalshi, api, pagination, historical-data

`/historical/markets` accepts `mve_filter=exclude` but returns HTTP 400 for `mve_filter=only`. To fetch KXMVE combos from the archive, query `/historical/markets?series_ticker=KXMVE...` instead. On `/markets/trades` and `/historical/trades`, `min_ts` is inclusive and `max_ts` is exclusive, both in whole seconds. Settled markets and trades older than the nightly cutoff (`GET /historical/cutoff`) are served only by `/historical/*`. Trade payloads use fixed-point strings (`count_fp`, `yes_price_dollars`) and include `taker_side`.
