Polymarket CSV Export: Pull Settled Positions and Realized PnL Out of Any Wallet

Why is prediction market record-keeping so painful?

When you trade on Polymarket, every position is a chain of on-chain events: share splits, merges, buys, sells, USDC transfers, and redemptions once a market resolves. Your wallet never hands you a profit-and-loss statement. Polymarket does not issue a 1099 for on-chain activity, and Kalshi keeps its records in a separate format on a separate venue. At record-keeping time you are left rebuilding what happened from a blockchain explorer or a pile of half-matched fragments, and the numbers rarely reconcile on the first pass.

General-purpose crypto tools make it worse rather than better, because they read the movements and not the meaning. A redemption that paid a dollar a share looks like an ordinary token transfer. A multi-outcome question, where a single logical trade fragments into many sub-market events, reads as a scatter of unrelated positions. What you actually want is a list of markets you closed, what you paid, and what came back.

The stakes are concrete because the instrument is concrete. Prediction market shares pay $1 if the outcome happens and $0 if it does not, so realized gains and losses on Polymarket are real, reportable dollar amounts. Active traders running hundreds of fills across dozens of markets need something that speaks the native language of the exchange, not a generic wallet parser bolted on after the fact.

What does the WhaleTracks export actually produce?

The export turns a Polymarket wallet's settled positions into a structured, downloadable file. Its scope is exactly that and worth stating before anything else: closed, resolved markets. Open positions are not in the file. It is a record of what finished, not a snapshot of what you are carrying, and the Portfolio Tracker at /portfolio is where the open book lives.

Each row carries eight fields: the settlement date, the market title, the outcome you held, whether that outcome won or lost, your average entry price, the dollars you put in, the realized profit or loss on the position, and the market's slug so you can find it again. A final TOTAL row sums realized PnL across every position in the file. CSV drops straight into a spreadsheet; the same data is available as JSON for scripts and notebooks, wrapped with the wallet address, the number of settled positions, and the total realized PnL.

What the file does not contain is as important as what it does. There is no date-range picker, no fee column, no quantity or per-fill breakdown, no acquisition-versus-disposal timestamps, and no tax-lot matching. It is a clean statement of settled outcomes and realized results — the arithmetic your own records or your preparer can build on — not a finished tax computation, and it should not be described as one.

Kalshi is not exported here at all. Kalshi publishes no per-account data through its public API, so there is no record of an individual Kalshi account for any third-party site to read. Everything Kalshi contributes elsewhere on WhaleTracks is anonymous, market-level flow.

How do you export a Polymarket wallet to CSV?

The simplest route is the Portfolio Tracker. Add a wallet at /portfolio by pasting its public address, and the chip for that wallet carries a CSV link. Click it and the file downloads. There is nothing to configure, because there is nothing to configure: the export always covers that wallet's settled positions, up to the five hundred most recent the venue's public API returns, and it skips positions where the cost was under a dollar so dust does not pad the file.

For JSON, request the same endpoint with the format set to json instead of csv. The payload holds the wallet address, the count of settled positions, the total realized PnL, and the same records as an array — which is the shape you want if you are loading a wallet into a notebook rather than a spreadsheet.

Exporting is not only a records feature, it is a research feature, because the endpoint works on any public Polymarket address and not only your own. Point it at a sharp trader's wallet and you get their settled history in the same clean format: which markets they closed, what they paid, and what each one returned. This is the practical core of a polymarket whale tracker workflow — instead of squinting at a block explorer, you get a sortable file. It pairs naturally with Sharp Score and the Watchlist, which help you decide which wallets are worth exporting in the first place.

A common pattern: export your own wallets periodically for your records, then run targeted exports of two or three wallets you follow. The first file keeps your books clean. The others feed your read on what experienced traders actually did, in a format you can analyze rather than screenshot.

How does the export decide what won and what a position returned?

Settled PnL is the realized result on markets that have already resolved. When a market closes, winning shares redeem for $1 and losing shares expire at $0. The export reads the venue's own record of each closed position, so the realized figure in the file is the number Polymarket itself computes for that position rather than something reconstructed from raw transfers.

The win-or-loss column is derived from where the outcome finally settled: above the midpoint means the outcome happened, below means it did not. That is a deliberately simple rule, and it is the reason multi-outcome questions come out coherent — a leg that converted or resolved through a grouped market still lands on the side it actually settled on, rather than appearing as a stray token movement with no context.

Because the file is a per-position statement, you can audit it against the venue directly. Each row carries the market slug, so any figure you doubt can be traced back to the market it came from. That transparency matters more than a summary you have to trust, and it is far more defensible than a number typed into a cell from memory.

How can wallet exports make you a sharper trader, not just keep records?

Clean data is an edge before it is ever a record. Exporting a wallet's settled history lets you study how a trader actually operates: typical position size, the prices they tend to enter at, how their winners and losers are distributed rather than just netted. Reading a wallet at this resolution turns a vague sense that someone is smart money into a concrete, testable description. This is intelligence, not blind copying: the goal is to understand a decision, weigh it against your own view and the live market, and then decide for yourself.

This is also where copy trading prediction markets goes wrong for most people. Mirroring fills without context means inheriting someone's risk, timing, and mistakes with none of their reasoning. Used as research, an export answers the questions that make following someone intelligent instead of reflexive: is this trader consistent across many markets or riding one lucky line, and does their entry still make sense at the current price? Combine the export with the Live Feed and an Alerts rule to catch new activity from wallets you have already studied, so you are reacting to context you understand rather than a bare notification.

Any pattern you find in historical exports is descriptive, not predictive. Past performance does not guarantee future results, and any backtest or simulation you build from this data is hypothetical. A wallet that printed last quarter can give it all back next quarter. Nothing here promises profit, and no analysis of prediction markets removes the risk that a position resolves against you. Treat exports as sharper inputs to your own judgment, not a shortcut around it.

What are the limits of the export?

This is a records tool, not tax advice, and it is not a tax report. It gives you settled outcomes, average entry, cost, and realized PnL per market. It does not compute lots, does not model fees, does not carry the timestamps a holding-period question needs, and does not know your jurisdiction or your filing status. Take the file to a qualified professional as source data, not as a finished return.

Coverage has hard edges. The export reads the venue's public closed-position record, capped at the five hundred most recent, and drops positions that cost under a dollar. A very active wallet's oldest history will therefore fall outside the file, and anything that never settled is not in it at all. Kalshi cannot be exported for the structural reason above, and Manifold is a play-money venue whose activity is not real financial trading and should never be folded into a records file.

Finally, an export is a snapshot of what has already happened, not a forecast of what will. It sharpens your records and your research, and it makes the numbers traceable, but it does not tell you which side of a market to take or guarantee any outcome. Past performance does not guarantee future results, simulations are hypothetical, and every open position still resolves to $1 or $0 on its own terms. Use it to trade and file with better information, and keep the risk decisions yours.