Skip to main content
The polymarket_polygon.market_details table describes every Polymarket market. It combines Polymarket’s own listing data (market, event and series details) with on-chain data on how each market was created and resolved. There is one row per outcome token (outcome_id), so each market has two rows, one per side. Each row is unique on (market_id, outcome_index). Combos (multi-leg parlays) are in combo_details, with the same layout. Markets on Polymarket’s newer Protocol V2 contracts are included (contract_version = 'v3' in market_trades). A market moved to Protocol V2 keeps its original token ids. Columns from Polymarket’s listing data show the latest listed values: gamma_market_id, the event and series columns, strikes, sports, fees and resolution settings. They are null for markets Polymarket does not list.
To find the winning side, use outcome_index and settlement_value_usd, not the outcome_name label. A filter like outcome_name = 'Yes' silently misses Up/Down, Over/Under and team-name markets.
Column groups:
  • Ids: market_id (the condition id, the market’s on-chain id, as a 0x... string), gamma_market_id (Polymarket’s own market id), outcome_id (the token), outcome_index, question_id, and neg_risk_market_id for markets that are one outcome of a mutually exclusive event.
  • Event and series: event_id, event_title, event_slug, event_description, parent_event_id, series_id, series_title, frequency, yes_sub_title, tags, category.
  • Lifecycle: status, archived, closed, accepting_orders, market_start_time, market_end_time, and on resolution outcome, settlement_value_usd and settlement_ts.
  • Strikes: strike_type, floor_strike, cap_strike, underlying and expiration_value for price, Up/Down, bracket, spread and Over/Under markets.
  • Sports and elections: sports_market_type, competition, home_team, away_team, teams, score, scheduled_start_time, game_end_time, event_metadata, market_metadata, election_type, election_country.
  • Fees: fee_type, fee_rate, fee_exponent, maker_rebate_rate, is_fee_taker_only, and the older maker_base_fee_bps and taker_base_fee_bps.
  • Resolution oracle (UMA): settlement_source, uma_bond, uma_reward, liveness_seconds.

Table Schema

Table sample

Joins

Join trades, positions and candles on outcome_id. market_id is a VARCHAR here but a VARBINARY in market_trades and market_actions. To join those on market_id, use CAST(market_id AS VARCHAR) on their side.

Example queries

Markets settled in the last 7 days, with the winning side:
Open crypto price markets by underlying asset and series frequency:

Previous version

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