Skip to main content
The prediction_markets.markets table lists Polymarket and Kalshi markets in one table, with the same column names for both venues, so one query covers both. It has one row per binary market, unique on (venue, market_id). On Polymarket, market_id is the market’s condition id. For Polymarket Combos (multi-leg parlays, is_parlay = TRUE) it is the combo’s condition id. On Kalshi, it is the market ticker. This table holds market names and attributes. prediction_markets.trades and prediction_markets.ohlcv_hourly hold trades and prices only. Join them to this table on (venue, market_id). Every market is shown from its Yes side. On Polymarket, Yes is the market’s first token (outcome_index = 0), the side settlement is decided against. So yes_outcome_id, resolved_outcome and settlement_value_usd always agree. On Kalshi, the table covers every single market Kalshi has listed, traded or not, plus every parlay that has traded at least once. Polymarket rows take their event, series and strike details from Polymarket’s own listing data. So event_id, event_name, series_id, frequency, strike_type, floor_strike and cap_strike are filled for Polymarket as well as Kalshi. event_id is Polymarket’s event id. It is set on every market Polymarket lists, not only on multi-outcome events.
For markets without a natural Yes (team vs team, candidate vs candidate), Yes is simply whichever side the venue listed first. Check yes_outcome_name before reading the Yes side as an affirmative answer.

Table Schema

Table sample

Example queries

Previous version

Columns of the previous version, for queries that still use it. The migration guide maps each old column to its new name.