Polymarket historical data,
for the crypto Up/Down markets.
A day-by-day archive of Polymarket’s crypto Up/Down markets: the order books and trade prints a strategy would have met, the Chainlink feed those markets settle on, and the per-market metadata that ties the two together. Deliberately narrow — elections, sports and other event markets are not in it.
What one archived day contains
Each archived UTC day is a set of files per asset and dataset. Which assets and which days YOUR key reaches comes back from /v1/meta, so the history you can pull is never something you have to take on a page’s word.- book
- Full-depth order-book snapshots
- price_change
- Order-book deltas with best bid/ask
- best_bid_ask
- Top of book, unthrottled — the same best bid/ask price_change carries, at every update rather than the capture cadence; prices only, no sizes, so depth still needs book or price_change
- last_trade_price
- Trade prints, unthrottled
- markets
- Per-market metadata, strike and settlement outcome
- prices
- Settlement feed, tick by tick (instantaneous Chainlink stream)
- twap60s
- TWAP 60s settlement stream — settles both 5-minute and 15-minute markets
- klines
- OHLC candles derived from the settlement feed, with a tick count — no trade volume; the settlement feed is a price feed
A real day, opening rows
The first rows of real files from the public sample day — the same layout and formats a key downloads. Switch tabs to see each dataset’s fields.| feed_ts_ms | value | full_accuracy_value | server_ts_ms | recv_ms |
|---|---|---|---|---|
| 1788825600000 | 79094.22130500078 | 79094221305000785000000 | 1788825600909 | 1788825601123 |
| 1788825601000 | 79093.40661608898 | 79093406616088985000000 | 1788825602362 | 1788825602596 |
| 1788825602000 | 79089.24902162 | 79089249021620000000000 | 1788825603077 | 1788825603427 |
| 1788825603000 | 79083.93494677 | 79083934946770000000000 | 1788825604506 | 1788825604835 |
| 1788825604000 | 79082.44447689746 | 79082444476897465000000 | 1788825605131 | 1788825605328 |
Opening rows from the real 2026-09-08 (UTC) files. Values are copied verbatim. The complete files: Polymarket sample data download — check the checksums yourself. The same sample is also on Kaggle (decompressed) and Hugging Face.
What this history is good for
Only the crypto Up/Down markets, and why
The archive covers Polymarket’s crypto Up/Down markets: will an asset finish above or below its price to beat over a fixed window, decided against a Chainlink price. It does not cover elections, sports or any other event market. If those are what you need, this is the wrong archive, and it is better to learn that here than after a download.
The narrow scope is what makes the history checkable. These markets resolve on a published number rather than a judgement call, and that number is in the same archive — so where a market’s strike and its settlement stream are both present, its outcome can be recomputed instead of trusted.
Depth, not just a price line
A price series — one mid or last price per interval — is enough to chart a market and not enough to backtest one: whether an order would have filled depends on the depth resting at that moment. The archive keeps full-depth book snapshots and the deltas between them, captured at a cadence that has changed over the archive, with top of book and trade prints as streams of their own.
History you can audit
Each file is listed with its byte length and a SHA-256, so you can prove you received what was published. Gaps stay gaps — nothing is interpolated to make a day look whole — and frames keep the order they arrived in, out-of-order ones included.
How to pull a stretch of history
Ask /v1/meta which days your key reaches, then list files across them with from and to. Each result carries a sha256 and a download url.# the oldest and newest day your key reaches FROM=$(curl -s -H "Authorization: Bearer $OT_KEY" \ https://outcometick.com/v1/meta | jq -er .firstDay) TO=$(curl -s -H "Authorization: Bearer $OT_KEY" \ https://outcometick.com/v1/meta | jq -er .lastDay) # BTC trade prints across that range in one listing — a single call has a day cap, so split a long window (see /docs) curl -H "Authorization: Bearer $OT_KEY" \ "https://outcometick.com/v1/files?venue=polymarket&dataset=last_trade_price&asset=btc&from=$FROM&to=$TO" # download the first file of that listing — /v1/dl 302s to storage URL=$(curl -s -H "Authorization: Bearer $OT_KEY" \ "https://outcometick.com/v1/files?venue=polymarket&dataset=last_trade_price&asset=btc&from=$FROM&to=$TO" \ | jq -er '.files[0].url') curl -L -H "Authorization: Bearer $OT_KEY" "$URL" -o trades.jsonl.gz
None of this needs a key to check first. The public sample archive is one real day in the same layout and formats as the paid archive — parse it, check the checksums, recompute a market or two, then decide.
Questions about the history
What does the Polymarket historical data include?
Full-depth order-book snapshots and the deltas between them, top of book, trade prints, per-market metadata with strike and settled outcome, the Chainlink settlement streams, and OHLC candles derived from the settlement feed — for Polymarket’s crypto Up/Down markets.
Does it cover elections, sports or other Polymarket markets?
No. Only the crypto Up/Down markets. The assets currently covered are counted at the top of this page, and /v1/meta lists the ones your key reaches.
How far back does it go?
The first complete archived day is shown at the top of this page. What a key reaches depends on what was bought: the subscription covers a rolling window of the most recent archived days, and any earlier stretch can be bought once as a date range.
What format are the files?
Order books, trade prints and market metadata are gzipped JSON Lines; the settlement streams and candles are gzipped CSV. Each file is listed with its size and SHA-256, and the field-by-field schemas are in the docs.
Can I look before paying?
Yes. The public sample archive is one real day in the same layout and formats, the opening rows of its files are shown above, and ot run replays it locally through the backtest engine.
Is this an API or a bulk download?
An API over files. One bearer key; /v1/files lists files by venue, dataset, asset and date, and each comes back with a download url. There is no live stream — this is an archive.
Rather have the answer than the history?
Paste a strategy and it runs against this same archive in a sealed sandbox — fills matched against the depth that was there, priced per market-day scanned.