predictparity.com APIpredictparity.com ↗
Access PredictParity prediction market data: search markets, get detailed outcomes with APY, browse tags, and query trader leaderboards via 4 REST endpoints.
curl -X GET 'https://api.parse.bot/scraper/51e2bb62-bec2-4e76-9175-ec870cb81137/search_markets' \ -H 'X-API-Key: $PARSE_API_KEY'
Search and list prediction markets with optional filters for tags, status, and text search. Returns paginated results sorted by the specified field. Useful for finding weather prediction markets, political markets, and more.
| Param | Type | Description |
|---|---|---|
| tags | string | Comma-separated list of tag slugs to include (e.g. highest-temperature,weather,politics). Use get_tags endpoint to discover available tag slugs. |
| limit | integer | Number of results per page (1-100). |
| query | string | Text search query to filter markets by question/title. |
| offset | integer | Pagination offset (0-based). |
| status | string | Market status filter. Accepts: active, resolved, closed. |
| sort_by | string | Field to sort by. Accepts: volume24h, volume1h, liquidity, endDate, startDate. |
| sort_order | string | Sort direction. Accepts: desc, asc. |
| excluded_tags | string | Comma-separated list of tag slugs to exclude (e.g. sports,crypto). |
{
"type": "object",
"fields": {
"limit": "integer current limit",
"offset": "integer current offset",
"markets": "array of market objects with id, question, outcomes, volume, tags, etc.",
"has_more": "boolean indicating if more results are available"
},
"sample": {
"limit": 3,
"offset": 0,
"markets": [
{
"id": "95185f4d-6fcb-4951-8769-7ca490fa2c35",
"slug": "highest-temperature-in-hong-kong-on-june-6-2026-30c",
"tags": [
{
"slug": "weather",
"label": "Weather"
}
],
"status": "active",
"volume": 113536.17,
"endDate": "2026-06-06T12:00:00.000Z",
"eventId": "fac5dacc-11df-45a9-9558-42d9db7acdea",
"outcomes": [
{
"result": null,
"spread": 2000,
"midPoint": 999000,
"isPrimary": true,
"outcomeId": "a151decf-67b6-427b-bed9-8ec5c79d135a",
"outcomeName": "Yes"
}
],
"platform": "polymarket",
"question": "Will the highest temperature in Hong Kong be 30°C on June 6?",
"liquidity": 4279.83,
"startDate": "2026-06-05T04:17:22.956Z",
"volume24h": 109380.66,
"eventTitle": "Highest temperature in Hong Kong on June 6?",
"displayNameShort": "30°C"
}
],
"has_more": true
}
}About the predictparity.com API
The PredictParity API exposes 4 endpoints covering prediction market search, individual market details, tag discovery, and trader analytics. The search_markets endpoint lets you filter across weather, geopolitics, crypto, and other market categories by tag slug, status, sort field, and text query. Each market record includes outcomes with midPoint, spread, and APY alongside liquidity and net flow volume data.
Market Search and Discovery
The search_markets endpoint accepts up to eight parameters: tags and excluded_tags accept comma-separated tag slugs (e.g., highest-temperature,weather), status filters by active, resolved, or closed, and sort_by accepts volume24h, volume1h, liquidity, endDate, or startDate. Results are paginated via limit and offset, and the has_more boolean tells you whether another page exists. The response markets array contains each market's id, question, outcomes, volume, and associated tags.
Market Details
get_market takes a market slug (available from search results) and returns the full record: description with resolution criteria, outcomes array with per-outcome midPoint, spread, and apy, plus liquidity, total volume in USD, and a netFlowVolumes object showing directional volume flow. An optional platform parameter currently accepts polymarket, allowing cross-platform lookups on supported markets.
Tags and Traders
get_tags returns a flat list of tag objects, each with a slug, human-readable label, and activeMarketCount. This is the canonical way to discover valid slugs before passing them into search_markets. The get_traders endpoint lists platform traders with analytics, badges, and trading traits, sortable by volume, pnl, or rank, and supports text search via the query parameter alongside standard limit/offset pagination.
- Monitor active weather prediction markets by filtering
search_marketswith thehighest-temperatureorweathertag slugs. - Track APY and spread on geopolitical outcomes by calling
get_marketwith a slug likewill-china-invade-taiwan-before-2027. - Build a leaderboard dashboard by querying
get_traderssorted bypnlorrankwith paginated results. - Discover which market categories are most active by checking
activeMarketCountfromget_tags. - Alert on newly opened crypto prediction markets by polling
search_marketswithstatus=activeandsort_by=startDate. - Analyze net directional sentiment by reading
netFlowVolumesfromget_marketacross a portfolio of market slugs. - Find underexplored market niches by combining
excluded_tagsandsort_by=liquidityinsearch_markets.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does PredictParity have an official developer API?+
What does `get_market` return beyond a market's current price?+
get_market returns per-outcome midPoint, spread, and apy, the full description with resolution criteria, current liquidity, total volume in USD, and a netFlowVolumes object that breaks down directional volume flow for the market.Can I retrieve historical trade or order book data for a specific market?+
How does tag filtering in `search_markets` work, and where do I get valid tag slugs?+
tags and excluded_tags parameters accept comma-separated slugs. Call get_tags first — it returns every available slug alongside its label and activeMarketCount. Slugs from that response are the valid inputs for search_markets filtering.Does the API cover markets from platforms other than PredictParity itself?+
get_market endpoint accepts an optional platform parameter that currently supports polymarket. Cross-platform search filtering and trader data from external platforms are not currently covered. You can fork this API on Parse and revise it to add broader multi-platform support.