Skip to main content
Prediction Market data is currently in beta. It is actively being worked on and improved, but may be unreliable. Polymarket and Kalshi data are live.At least for the time being, this endpoint requires a Growth or Enterprise plan. Learn more.
This endpoint requires a Growth or Enterprise plan. Learn more.

Returns

PredictionMarketFilterConnection
See PredictionMarketFilterConnection

Arguments

PredictionMarketFilters
A set of filters to apply. See PredictionMarketFilters
String
A phrase to search for. Can match market label, outcome labels, or event label.
[String!]
A list of market IDs to filter by.
[String!]
A list of market IDs to exclude from results.
[String!]
A list of event IDs to filter markets by (returns markets belonging to these events).
[String!]
A list of event IDs to exclude (excludes markets belonging to these events).
[PredictionMarketRanking!]
A list of ranking attributes to apply. See PredictionMarketRanking
Int
The maximum number of markets to return.
Int
Where in the list the server should start when returning items.

Example: Top markets by 24h volume

Test this query in the Explorer →
Example Response (truncated)

Example: Search markets by text

Example: Filter by category and status

Example: Filter by time range and liquidity

Usage Guidelines

  • Response limit: 100 markets per request (configurable with limit parameter)
  • Use trendingScore24h or volumeUsd24h rankings for discovering active markets
  • Apply quality filters like minimum liquidity (liquidityUsd: { gt: 10000 }) to focus on liquid markets
  • Use phrase parameter to search by market question, event label, or category
  • Filter by status: OPEN to exclude resolved/closed markets
  • Use categories filter to narrow down to specific topics (e.g., “sports”, “politics”, “crypto”)
  • Combine multiple time windows (5m, 1h, 4h, 12h, 24h, 1w) to analyze market trends over different periods

Market Status Values

See the PredictionEventStatus enum for all possible status values and their meanings.

Scoring Metrics

  • trendingScore - Measures what’s “heating up” - prioritizes growth velocity over absolute size (a small market with 10x volume growth scores higher than a large market with flat volume)
  • relevanceScore - Measures what “matters” - based on absolute size and capital at stake, with no growth multipliers (large, established markets rank high even if quiet)
  • competitiveScore - Measures genuine uncertainty - higher when prices are near 50%, trading is balanced on both sides, and there’s active price discovery

Troubleshooting Tips

volumeUsd24h shows trading volume in the last 24 hours, while volumeUsdAll shows total lifetime volume for the market. For trending markets, use 24h metrics. For market maturity analysis, compare volumeUsdAll with time-based volumes.
Some markets use generic Yes/No outcomes without custom labels. Check both outcome0.label and outcome1.label - if null, treat them as Yes/No or reference the market question for context.
Use the change metrics like volumeChange24h, liquidityChange24h, and uniqueTradersChange24h. Positive values indicate growth. Combine with trendingScore for markets with accelerating activity.