0.85¢ per request

Kalshi historical data

Read the trades behind a settled market.

Get dated Kalshi trades for a market ticker. Our worked example reads an October Fed-rate contract, with contract counts, yes/no prices and a cursor for the next page.

One TaskFuel account and prepaid balance. Your agent shows the price before it pays.

Works with

Choose the history you need.

Trade records, candles and a complete exchange archive answer different questions.

Access and tested prices checked on 11 November 2026.
OptionPrice & billingChoose it forGood to knowAccess
Predexon via BlockRunThrough TaskFuel$0.0085 / requestPer request from your TaskFuel balanceFive rows requested per page in this test.One TaskFuel balance; two trade-history pages inspected.Full archive coverage and candlestick output were not tested.TaskFuel
Predexon directOwn API keyProvider referenceFree trade endpointDocumented as free and unlimited on every planDirect API authentication required.A direct route for repeated trade-history queries.Separate credentials; this test used the TaskFuel route.Direct
Kalshi historical APIDirect exchange APIProvider referenceSee exchange documentationDirect access under Kalshi’s API termsThe archive publishes cutoffs by data type.Exchange-native historical trades and market candles.Live and historical routes have different data windows; no direct historical call was tested.Direct

Kalshi historical data: what your agent gets.

Ten records from one settled contract, across two pages. The provider still reported more history after page two.

  • Read trades within a date range

    A market ticker and Unix timestamps select the history. Each row includes trade ID, contract count, yes/no prices, taker side and trade time.

    $0.0085 / request
  • Continue with the returned cursor

    The next page uses the same filters and the returned pagination key. The documented maximum is 500 rows per page; our test used five.

    $0.0085 / next page

October Fed-rate trade history, tested.

The first page returned five trades for the requested ticker. A second request returned five more with distinct trade IDs. Every timestamp fell within the requested window.

TaskFuel test run ·

Charged $0.0085

Your agent asked

Read five historical trades for the October Fed-rate contract above 4.25%
Data from
Predexon via BlockRun

What came back

Contract
Fed upper bound above 4.25% after the 28 October 2026 meeting
First returned trade
94 contracts; yes $0.01, no $0.99; taker side yes
Trade time
28 October 2026 at 17:49:34 UTC
Pagination test
5 + 5 records; 10 distinct trade IDs; more history available

The receipt is for page one. Page two cost another $0.0085. Two pages are a sample of one contract’s history.

Try the API request Quote first, then run

1. Check the price

Use your TaskFuel API key as TASKFUEL_API_KEY in your terminal or server. Keep it out of browser code. This request checks the price without paying.

Exact first-page request. start_time=1790812800 and end_time=1793232000 mean 1 October and 29 October 2026 at 00:00 UTC. Both parameters use seconds.

curl --fail-with-body https://app.taskfuel.ai/v1/call \
  -H "Authorization: Bearer $TASKFUEL_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary @- <<'TASKFUEL_REQUEST'
{
  "url": "https://blockrun.ai/api/v1/pm/kalshi/trades?ticker=KXFED-26OCT-T4.25&start_time=1790812800&end_time=1793232000&limit=5",
  "method": "GET",
  "dryRun": true
}
TASKFUEL_REQUEST

2. Run the request

Review amount_usd in the quote. To pay and run, change dryRun to false and add maxAmountUsd with that approved amount inside the same JSON object. Keep the inputs unchanged; this limit applies to one call.

3. Read the result

Read trades[].trade_id, ticker, count, yes_price, no_price, taker_side and created_time. Here count is contracts and 0.01 is $0.01 per contract, or 1¢. created_time is Unix seconds; created_time_ms is milliseconds. For the next page, URL-encode pagination.pagination_key and send it as pagination_key with the same filters. Each page is a new paid request. pagination.has_more was true on both tested pages.

Read the Kalshi trade response contract

Setup and API reference · Job polling and timeout recovery

Try it in your next task.

Sign in to TaskFuel and copy the connection prompt into your agent. Approve the connection, then ask for the work you need.

01

Name the task

Tell your agent what the output needs to contain.

02

See the price

Your agent shows the provider and price before spending.

03

Review the response

Check the output against your task. The call reports its cost and remaining balance.

When to use it.

Market research

Read prices before settlement.

Your agent retrieves dated trades for the chosen ticker and puts contract counts next to prices.

CSV preparation

Turn returned trades into rows.

An agent can write the returned JSON to CSV with trade ID, ticker, UTC time, count and yes/no prices. The tested result is a paginated JSON response.

Choosing a series

Separate trades from candles.

Individual fills describe executions. A candlestick series aggregates a time interval, while an order book describes available bids and asks. This example reads trades.

Good Questions.

How do I get Kalshi historical data?

Select a market ticker and a UTC date range, then read trade pages. TaskFuel provides the tested Predexon route through BlockRun. Kalshi also documents its own historical API.

Does this include every historical Kalshi market?

The test covers one settled October 2026 Fed-rate contract. It does not establish earliest coverage, complete market coverage or a full archive export.

Why might older data be missing from Kalshi’s live API?

Kalshi separates live and historical data. Its historical cutoff endpoint publishes a separate cutoff for each data type. Older trades belong on the historical trades route; market candles have their own historical route.

Can I get Kalshi historical data as CSV?

The tested endpoint returns JSON. Your agent can convert returned trade rows into CSV. A complete export requires paging through the selected range until the provider reports no more results.

Can I use Predexon directly?

Yes. Predexon’s direct trade endpoint requires its own API key. Its documentation lists this endpoint as free and unlimited on every plan, so direct access may be a better fit for repeated exports.

What did the historical-data requests cost?

Each five-row request cost $0.0085 on 11 November 2026. Two tested pages cost $0.017 total. Your agent shows the price for your own request before it pays.

Your agent can do things it couldn’t this morning.

$1 in free credit, no card required.

Start for Free