Skip to main content

Choose a workflow

Find a Polymarket condition

Resolve a Polymarket slug or URL into condition IDs.

Audit a timestamp range

Pull raw records across an inclusive timestamp window with cursor pagination.

Find asset IDs

Extract CLOB token IDs for per-outcome Polymarket orderbook summaries.

Build OHLC quotes

Get best bid, best ask, midpoint, spread, and OHLC candles.

Check data quality

Validate stored dates and April 2026 known windows before a backtest.

Find a Polymarket condition

Find Polymarket asset IDs

Polymarket summaries are per outcome token. First use the condition ID to pull a small raw page, then collect the unique asset_id values from the returned events.
A binary Polymarket usually has two asset_id values. The API does not label which token is which outcome in raw orderbook records, so join against Polymarket market metadata when you need outcome names.

Audit a timestamp range

Range endpoints accept Unix seconds or milliseconds. Use next_cursor unchanged while has_more is true.

Build OHLC quotes

Polymarket orderbook summaries require a condition ID and an asset_id. Kalshi summaries require a ticker.

Check data quality

1

Check stored dates

Call get_market_date_range for the condition ID or ticker.
2

Sample raw data

Pull a small page from the exact UTC date or timestamp range you need.
3

Inspect summary buckets

Confirm quote_count, is_forward_filled, and the OHLC fields before using the data in a backtest.
Affected Kalshi records from 2026-03-31 through 2026-04-24 can have null price payloads even when quote counts are nonzero.
Some Polymarket markets have gap-marked or missing data during the April 2026 collector instability window. Inspect gap_start and gap_end records when auditing this period.
See Data Quality for the full incident notes.