Share a Kalshi market link and time range to compare past buy and sell prices for the Yes answer (the event happens), along with the number of contracts offered. Prices are rounded to whole cents.
Up to 0.01122 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
BlockRun
Kalshi Historical Orderbook Snapshots | BlockRun
Share a Kalshi market link and time range to compare past buy and sell prices for the Yes answer (the event happens), along with the number of contracts offered. Prices are rounded to whole cents.
You receive
You receive a page of snapshots for the market and period you choose. When records are available, they describe Yes-side bid and ask price levels, contract quantities, best quoted prices and snapshot times. Your Agent can arrange the records to compare changes in the rounded book over that period.
Start with your task
Review up to five records for [Kalshi market page link], from [start date and time with time zone] to [end date and time with time zone]. Compare prices people offered to buy and sell the Yes answer, and how many contracts were offered. Say if no records are returned.
What to know
Whole-cent rounding can widen spreads and merge neighboring price levels, so the result does not preserve native sub-cent precision. Records may be missing or the page empty; historical quotes do not guarantee fills or continuous coverage.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
Market and time rangequeryParams
object
Optional
Supply the Kalshi market ticker, start_time and end_time directly in this container. All three are needed for the chosen market and period; both times are integer Unix milliseconds. Optional limit sets page size.
Nested query objectqueryParams.query
object
Optional
This optional object does not flatten into the orderbook request. Put ticker, time range, page size and any cursor directly in queryParams.
No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.
Result schema
Field / Path
Type
Meaning
Orderbook snapshotsresult.snapshots
array
Returned snapshot collection for the requested market and range. An empty list contains no records for that response; it does not prove there were no orders or current bids and asks.
Page informationresult.pagination
object
Page count, requested limit and continuation information. These describe this response, not complete historical coverage.
Snapshots on this pageresult.pagination.count
number
Number of snapshots in the current response, not the total across the chosen period.
Page limitresult.pagination.limit
number
Snapshot page size reported by the supplier. It is an upper limit and does not promise that many records.
More pagesresult.pagination.has_more
boolean
Whether the supplier reports more records. Continuation also requires a returned nonempty pagination_key.
Next-page cursorresult.pagination.pagination_key
null
Opaque cursor for the next page, when supplied. Keep it unchanged with the same ticker and time range; null or an empty value cannot be used to continue.
Additional notes
Market and period
Provide the exact Kalshi market ticker, plus start and end times with a time zone. An event or series ticker is not the market identifier this request needs. The Agent converts both times to integer Unix milliseconds and sends ticker, start_time and end_time directly inside queryParams, not queryParams.query. Choose an end later than the start. Optional limit accepts an integer from 1 to 2,000; the supplier default is 100. A page limit does not guarantee a record count.
The supplier reports that this history begins on January 7, 2026, without specifying the exact cutoff instant. That date does not guarantee records for every market or period. Empty or partial results cannot establish that no orders existed, and a page cannot prove continuous coverage. This is a historical query, rather than a stream of current book changes.
Reading available snapshot records
The supplier describes each available snapshot with its market ticker and timestamp in milliseconds. yes_bids lists Yes-side bid price levels in descending price order; yes_asks lists Yes-side ask levels in ascending price order. Each level has a price in whole cents and size in contracts. Supplier documentation lists prices of 1–99 cents, but returned boundary prices can include 0 and 100; preserve them unchanged. For example, a returned price value of 50 means 50 cents ($0.50). Keep the unit explicit.
best_bid and best_ask are prices in cents. bid_depth and ask_depth are total bid-side and ask-side contract quantities, not dollar amounts or executed trade volume. sequence orders records that share a timestamp; it does not establish a globally unique or gap-free sequence. Read snapshots as orderbook observations rather than completed trades or guaranteed fills. Depth is supplier-reported and may differ from the sum of displayed level sizes; preserve it without replacing it with a recalculated total.
Whole-cent precision and availability
This endpoint rounds sub-cent prices to whole cents. The supplier says that rounding widens spreads and merges neighboring price levels, so the snapshots cannot reconstruct the original sub-cent prices or exact native book spread. Preserve returned levels and quantities rather than guessing the finer prices.
The supplier has announced that this endpoint will be deprecated, but has not supplied a cutoff date on this page. Its recommended sub-cent endpoint is a different capability; this Tool does not silently switch to it. Check current Tool availability before requesting the history.
Paste one direct Kalshi market link and provide the start and end dates and times, including the time zone. You do not need to find a market number or convert the times.
Review up to five records for [Kalshi market page link], from [start date and time with time zone] to [end date and time with time zone]. Compare prices people offered to buy and sell the Yes answer, and how many contracts were offered. Say if no records are returned.
Review the historical prices
Compare the returned prices for the Yes answer and how many contracts were offered at each time. Prices are rounded to whole cents, so smaller price differences may disappear. An empty result means no records were returned for this request.