Track prices

How to Track Polymarket Prices

Tracking Polymarket prices well means tracking the executable side, not the headline: live reads from the free /book endpoint, a recorded 250ms series for history, and alerts that fire on depth states rather than tick noise. This page fixes the three layers.

Figures measured as of 2026-09-24 on the published PolyOrderbooks archive.

The layers

Three layers, one clock

All three share the UTC second, so a "price now" read and a "price at 14:42:50" read are the same kind of object — the difference is only which clock you ask.

What to track

Price fields that matter

The field you trade is the executable side (0.99/0.995 bunching, 98.6% of the time); the field you display is the mid; the field that protects you is the depth behind the price. A tracker that only draws mid is a tracker that shows a line that no one could have traded.

The venue's mid-price explainer and the one-sided pages are the same lesson in two formats: price without book context is a guess.

Worked example

Track a market from open to resolution

Pick a live 5-minute window, poll /book each poll interval, and store bid/ask/mid/depth with a UTC timestamp. At resolution, pull the same market's recorded history and join: the tracker just validated itself against the archive's stored truth.

That self-validation is the honest test of any PDK — a tracking setup that cannot be reconciled to recorded history is one you cannot trust.

Honest

The honest warning

Live polling over the free API is rate-limited and forward-only: snapshot locally if you need the past, because the live endpoint will not sell you yesterday. The archive exists precisely to cover that form of amnesia.

FAQ

How do I track Polymarket prices live?

Poll the free official /book endpoint for current ladders; store bid, ask, mid, and depth with a UTC timestamp.

Can I reconstruct past prices later?

Only from recorded history — the archive's 250ms series keeps prices, books, and metrics on one grid.

What should my tracker show?

The executable side and the depth behind it; a mid-only line misrepresents a venue that is one-sided 16.9% of the time.