Order-book backtesting

PolyBackTest Alternative for Historical Polymarket Data

PolyBackTest is an independent archive of full-depth Polymarket order books for BTC and ETH Up/Down markets, built for backtesting. PolyOrderbooks archives Polymarket crypto markets broadly at uniform 250ms capture. The deciding question is scope: which slice of Polymarket, and at what measured resolution.

Last verified: September 24, 2026. Public pricing and features may change — follow source links for the provider's current documentation.

PolyOrderbooks is independent and is not affiliated with Polymarket or the providers compared on this page.

Overview

Quick comparison

PolyBackTest facts from its public pages (verified October 3, 2026); PolyOrderbooks facts from our product docs.

FeaturePolyBackTestPolyOrderbooks
Historical pricesYes — price history alongside order-book snapshots and trade records via REST, for tracked BTC/ETH Up/Down marketsYes
Historical L2 booksYes — full-depth bid/ask ladders stored per snapshot and queryable at any point in time; coverage limited to tracked BTC/ETH Up/Down crypto marketsYes — full bid/ask ladders
Capture / deliverySelf-reported and contradictory across its pages: the homepage states 1-minute resolution, while enterprise pages claim sub-second snapshot granularity250ms capture; 250ms query resolution on every plan, including free
REST APIYes — documented REST endpoints /v1/markets, /v1/snapshots, /v1/snapshot-at with API-key auth and timestamp filteringYes
Python toolingA Python SDK is referenced in product materials and the PolyMart listing; the sampled pages documented the REST interfaceOfficial Python SDK on PyPI
Bulk exportYes — bulk historical order-book data downloads advertised (tick-by-tick depth datasets)Enterprise S3 delivery (Parquet, CSV, JSON) — not on self-serve plans
Free tierYes — a free tier to test the API before paying ("Start free. No card. Keep the free tier forever.")Yes — Starter: 250ms L2, prices, and metrics at $0 (3-day history)
Starting paid priceNot stated on sampled public pages — plans gate behind signup; PolyMart lists the paid subscriptions as billed via Stripe$19/month Pro (public pricing at time of verification)
CoverageBTC and ETH Up/Down crypto markets (15-minute rounds per sampled market data)Polymarket crypto markets (Up/Down and related) — depth history, not metadata breadth
Historical coverageSelf-reported up to 150 days of history with 100,000+ markets and 644M+ snapshots; an accumulating archive, not a backfilled oneContinuous 250ms archive from 3-day Starter windows to 30–120-day paid windows; resolved markets stay queryable

Source (PolyBackTest): https://polybacktest.com/polymarket-snapshots-api

Purpose-built for a slice of Polymarket

PolyBackTest targets one workload: backtesting strategies on Polymarket crypto markets. It captures full bid/ask ladders for Bitcoin and Ethereum Up/Down rounds — 1-minute candles per its homepage, which is a different claim from the sub-second granularity on its enterprise pages — keeps data after markets resolve, and documents point-in-time queries such as the Snapshots API. If your strategy is exactly these markets and full depth is the whole requirement, PolyBackTest is built for that slice — verify its conflicting resolution claims (1-minute on the homepage vs sub-second on enterprise pages) and its self-reported up to 150-day window before committing.

The trade-off is the coverage envelope. Its sampled pages describe a BTC/ETH Up/Down subset and self-report a history window of up to 150 days across 100,000+ markets and 644M+ snapshots — an accumulating archive rather than a backfilled one. The same volume of our archive covers Polymarket crypto markets generally (not only Up/Down rounds) and predates the accumulating window.

Two claims to pin down before you commit

Resolution. PolyBackTest's own pages disagree: the homepage says “full historical order book depth at 1-minute resolution,” while the institutional pages describe sub-second snapshot granularity. Capture cadence decides whether your fills can be simulated at the precision you think they can, so this is the first thing to ask for a written answer on. PolyOrderbooks captures every 250ms, with 250ms query resolution on every plan including free, and reconciles ladders against the live book.

History depth. The self-reported up to 150-day window matters more for backtesting than for most workloads, because a long lookback is what separates a strategy test from a recent-market fit. Its enterprise copy claims full historical Polymarket coverage with sub-second granularity; its public pages report 644M+ snapshots across 100,000+ markets. Confirm which is true for the plan you will buy.

When PolyBackTest fits

Every item below is scoped to the covered BTC/ETH Up/Down subset — a smaller envelope than the ongoing archive described in the next section.

  • Backtests scoped to Polymarket BTC/ETH Up/Down crypto rounds
  • Full-depth order book preservation after markets resolve
  • Point-in-time replay queries over covered timestamps
  • Bulk order book dataset downloads for local processing
  • A free tier to validate responses before subscribing

When our archive fits instead

If your strategy spans markets beyond Up/Down rounds — or you do not want your history window and capture cadence decided by a provider's plan — PolyOrderbooks captures Polymarket crypto ladders every 250ms and serves them over REST with 250ms query resolution on every plan. Resolved markets stay in the archive, the schema is stable, and a free Starter tier plus a free BTC 5-minute L2 sample let you validate before paying.

The same reconciliation test we run on our own archive is the one worth running on any PolyBackTest sample you are offered: ask for data, check that no book has a bid at or above the best ask, and compare timestamp formats with your existing parser.

If you would rather describe the strategy than write the replay loop, Backtest AI tests a plain-English idea against the same archive and explains every run.

FAQ

What is PolyBackTest?

PolyBackTest (polybacktest.com) is an independent service launched February 2026 that archives full-depth Polymarket order books for BTC and ETH Up/Down markets and serves them through a REST API and bulk downloads, aimed at backtesting crypto prediction-market strategies.

Does PolyBackTest have historical Polymarket order books?

Yes, for the markets it tracks. It stores full bid/ask ladders per snapshot and documents point-in-time queries such as the Snapshots API. Coverage is limited to BTC and ETH Up/Down crypto markets, and its pages self-report up to 150 days of history across 100,000+ markets and 644M+ snapshots (figures from its public pages, not independently verified).

PolyBackTest vs PolyOrderbooks — which should I use for backtesting?

PolyBackTest is built for BTC/ETH Up/Down backtesting on the slice it covers — verify its own contradictory resolution claims (1-minute vs sub-second) and self-reported up to 150-day history window first. PolyOrderbooks archives Polymarket crypto markets more broadly at uniform 250ms capture with 250ms REST query resolution on every plan, keeps resolved markets, and adds a Python SDK, MCP server, and a free L2 sample.

What are PolyBackTest alternatives?

PolyOrderbooks for ongoing broader Polymarket crypto L2 over REST; polyReplay for closed BTC/ETH Up/Down tick archives (unreachable since July 2026); DepthFeed for event-driven full-depth capture across venues; Telonex for tick-level Parquet pipelines.

How do I validate PolyBackTest data before porting a backtest pipeline?

The same check applies to any provider: ask for a sample and verify a real order book never has a bid at or above the best ask. Run that test on PolyBackTest's free tier, and run it on our free BTC 5-minute L2 sample too so you can compare schemas and timestamp formats before rewriting any parser.