polygon.predictions.market_orderbook table provides orderbook snapshots for Polymarket prediction markets, capturing bid and ask price levels with their corresponding quantities at specific points in time.
Use this table to analyze market depth, liquidity distribution, bid-ask spreads, and order book dynamics across Polymarket prediction markets.
Table Columns
Data Notes:- Orderbook snapshots capture the state of the order book at specific timestamps
- Each row represents one price level on either the bid or ask side
- Prices are in dollars
- Multiple rows per market and timestamp represent different price levels
unique_key
| Column Name | Data Type | Description |
|---|---|---|
| project | VARCHAR | Project identifier, always ‘polymarket’. |
| protocol | VARCHAR | Protocol identifier, always ‘polymarket’. |
| order_date | DATE | Date of the orderbook snapshot. |
| market_unique_id | VARCHAR | Unique key for grouping related markets. |
| condition_id | VARCHAR | Unique condition identifier. |
| market_question | VARCHAR | Market question text. |
| token_id | VARCHAR | Token ID for this outcome. |
| token_name | VARCHAR | Combined outcome and question name. |
| token_outcome | VARCHAR | Token outcome name. |
| side | VARCHAR | Orderbook side (bid or ask). |
| price | FLOAT | Price level in dollars. |
| quantity | NUMBER | Quantity at this price level. |
| tick_size | NUMBER | Minimum price increment (tick size). |
| neg_risk | BOOLEAN | Whether this is a NegRisk market. |
| min_order_size | NUMBER | Minimum order size in dollars. |
| orderbook_hash | VARCHAR | Hash of the orderbook state. |
| order_timestamp | TIMESTAMP_NTZ(9) | Timestamp of the orderbook snapshot. |
| ingested_at | TIMESTAMP_NTZ(9) | Data ingestion timestamp. |
| unique_key | VARCHAR | Unique record key. |
Understanding Orderbook Data
Bid vs Ask
- Bid: Buy orders (traders willing to buy at these prices)
- Ask: Sell orders (traders willing to sell at these prices)
Market Depth
Market depth refers to the market’s ability to sustain large orders without significantly impacting the price. More quantity at each price level = greater depth = more liquidity.Price Levels
Each row represents one price level in the orderbook. A typical orderbook snapshot will have:- Multiple bid price levels (descending from highest)
- Multiple ask price levels (ascending from lowest)
Use Cases
- Liquidity Analysis: Measure market depth and available liquidity
- Market Making: Identify opportunities for market making strategies
- Price Discovery: Understand where supply and demand meet
- Market Quality: Assess orderbook quality metrics (depth, spread, levels)