Kalshi trade history: every export, and what each leaves out.

Your activity sits in the same account menu as Documents. Its download icon offers All time, Today, This week, This month, This year, Last year and Custom dates, and saves Kalshi-Recent-Activity-All.csv; the suffix follows the filter chip selected on the page. The file has 25 columns, among them Fee_In_Dollars, Direction, Price_In_Cents and, on settlement rows, the YES and NO contracts held with their average prices and Profit_In_Dollars.

It is the file that carries the opening trades of positions still open, which the P&L download leaves out. It does not match lots or compute basis, and its money arrives in two units: fees and amounts in dollars, trade prices in a column named for cents. The file is built in the browser from requests capped at 10,000 trades and 1,000 settlements per range; we have not tested an account over those counts.

Activity export

Your activity page: All time to Custom dates, saving Kalshi-Recent-Activity-All.csv with 25 columns of orders, trades, settlements, deposits, withdrawals and credits

Source

Activity rows

Orders, trades with their fee, and settlements with contracts held and profit; columns for deposits, withdrawals and credits

Source

How it builds the file

In the browser, from requests for up to 10,000 trades, 10,000 orders and 1,000 settlements in the range

Source

Each year on the Documents page has a download icon. It saves a zip named for the year’s dates holding one file, realized_pnl_2026-01-01_2027-01-01.csv for 2026. On the account in our capture, the rows sum exactly to the page: $14.60 with fees and $136.93 without, so $122.33 of fees in the year. Five rows from that file, account id removed:

What the rows show, read off the file:

• Settlements look like sales. A market that resolved appears as an exit at 1.00 or 0.00 with no close fee, because Kalshi charges no settlement fee.
• One position can be two rows. The two KXWCROUND rows share open and close times but not an entry price: each price is its own lot, with its own share of the fee.
• Counts and fees are fractional. 19.78 contracts, a 0.2526 fee. Rounding each row to cents before adding moves the total.
• Credits are not trades. A credit row has no ticker, no side and quantity 0, and its amount sits in both profit columns. This file carries a +5.00 credit and a later -5.00 reversal.
• Not every year gets a row. The account in our capture has 1099s for 2024 and 2025 and one P&L row, for 2026, its one year with closed positions.

P&L CSV columns

13: type, quantity_fp, market_ticker, side, entry and exit price, open and close fees, profit with and without fees, close and open timestamps, and a subtrader id

Source

Credit rows

type credit, quantity 0, no ticker or side, the credit as the profit

Source

Years listed

Years with closed positions: the account captured had 1099s for 2024 and 2025 and one row, for 2026

Source

How current

The 2026 download on October 8, 2026 already held closes from that morning

Source

Settlement

No fee

Source

Kalshi’s Get Fills reference says it in one sentence: “Fills that occurred before the historical cutoff are only available via GET /historical/fills.” Its Historical Data page gives the mechanism. GET /historical/cutoff returns one timestamp per data type, the fills one in trades_created_ts, and the cutoffs are “regularly updated, advancing forward over time.”

Passing min_ts=0 to /portfolio/fills does not reach past the cutoff; it returns the live tier and stops. Kalshi does not publish the window’s length. On the accounts Realize reads it has run about two to three months, so a year read from one endpoint is missing most of itself. The fills that fall through are the oldest ones, often the purchases behind positions still held, so the gap removes cost basis first.

• The tell: a market with a settlement and no fills. The settlement survived; the opening trade did not.
• The gap after a pause: a pull that stops for longer than the window misses the fills that crossed the cutoff while it was stopped, unless the next run compares its last sync with the current cutoff rather than with the last fill it saw.
• The fee: every fill carries fee_cost in dollars, the figure the Kalshi fees formula produces.

Fill history

Fills before a moving historical cutoff are served only by GET /historical/fills; the live window’s length is not published

Source

Each fill

Kalshi’s API reports the fee on every fill as fee_cost, in fixed-point dollars

Source

GET /portfolio/settlements returns only settlements still in the live data set, and Kalshi’s Historical Data page says “there is currently no historical endpoint with the same settlement-record fields.” Once a market ages out, its settlement row is gone from the API. Two things survive: GET /historical/positions, with each market’s position, realized profit and loss and fees, and GET /historical/markets, with the market’s result and settlement_ts.

The units change inside one record. In Kalshi’s Get Settlements reference, revenue is an integer number of cents, while fee_cost, yes_total_cost_dollars and no_total_cost_dollars are dollar strings. A script that subtracts cost from revenue without converting is off by a factor of 100.

The two position endpoints also make a check on a fill-built figure: the realized profit and loss of /historical/positions before the cutoff plus /portfolio/settlements after it. On one account that sum came to -$181.93, matching Kalshi’s own figure for the same trades to the cent. Credits sit on no endpoint, so this figure and any figure built from the API stay below Kalshi’s headline by the account’s credits.

Settlements

GET /portfolio/settlements returns only records still in the live data set

Source

Archived settlements

No historical endpoint carries the settlement record’s fields

Source

Archived positions

GET /historical/positions gives position, realized profit and loss, and fees

Source

Settlement money

revenue in integer cents; fee_cost and the YES and NO total costs in fixed-point dollars

Source

Kalshi’s fixed-point page says integer-cent fields cannot represent sub-cent prices, so on a deci-cent market the _dollars fields are the ones to carry, rounded once at the end. Direction comes from outcome_side, the exposure a fill leaves you with: buy YES and sell NO both read yes, which is why the deprecated action field alone does not tell a closing sale from an opening buy.

Contract counts

Fixed-point strings with 2 decimals; the smallest unit is 0.01 contract

Source

Prices

Dollar strings with up to 4 decimals; integer-cent fields cannot represent sub-cent prices

Source

Fill direction

outcome_side: buy YES and sell NO both read yes; action and side are deprecated

Source

Section 1256 treats a Section 1256 contract held at year end as sold at fair market value on the last business day of the year (26 U.S.C. §1256(a)(1)), so people filing that way need a price for each open position, and neither the P&L download nor the forms give one. Kalshi’s Get Market Candlesticks endpoint does: a period_interval of 1440 returns one candle a day. Two details decide whether the price is the right one.

• The day ends at Eastern midnight. The candle carrying December 31’s trading is stamped January 1 at 05:00 UTC. Read as a UTC date it names the wrong day.
• Old candles move too. A market settled before the cutoff answers only on /historical/markets/{ticker}/candlesticks, with a different response shape.

A market that did not trade on the day has no close. Realize leaves that position off Form 6781 and says so, rather than substituting cost or an older price.

Daily price history

A public daily candlestick for each market, closing at its last traded YES price

Source

Candles

1, 60 or 1440 minutes; a market settled before the cutoff only on the historical candlestick route

Source

December 31 price

Not on Kalshi’s statement or forms for a position still open

Source

Keys are created under Account & security, in the API keys section. As captured on October 8, 2026, the Create API key dialog opens with the key type set to Ed25519, “Recommended,” and with both Read all data and Full access checked; Full access includes Trade and Transfers. A key that only reads keeps Read all data and has Full access unchecked. Kalshi’s dialog defaults to Ed25519; Realize connects with either RSA or Ed25519 keys.

Each request is signed over the millisecond timestamp, the method and the full path, /trade-api/v2/portfolio/fills rather than /portfolio/fills, with the query string left out of the signature and kept on the URL. An Ed25519 key signs that string directly; an RSA key signs it with RSA-PSS over SHA-256. Lists are cursor-paged, 1 to 1,000 rows a page. Most requests cost 10 tokens against the read budget, and a 429 carries no Retry-After header, so a cursor walk backs off on its own clock.

Key types

Ed25519, recommended and selected by default, or RSA 2048 for RSA-PSS clients

Source

New API key defaults

Ed25519 key type, with both Read all data and Full access checked

Source

Signature

Timestamp, method and path, signed without the query string

Source

Rate limits

Most requests cost 10 tokens; a 429 carries no Retry-After header

Source

Realize connects read-only and pulls the raw API data rather than an export:

• Every fill from both /portfolio/fills and /historical/fills, with the archive read again whenever a pause could have let fills cross the cutoff.
• Every live settlement, and the result of any market whose settlement has aged out, from /historical/markets.
• The daily close of every market held on December 31, from the live or historical candlestick route.

From those it matches lots first in, first out and prices the year under each common treatment, whichever route a return uses. The same year, in dollars, is on Kalshi taxes, and a quick range is on the Kalshi tax calculator.