Polymarket Scraper | Fast & Reliable

Overview

Polymarket is a prediction market where traders price real-world outcomes in real time. This actor collects structured market records from Polymarket search results, category pages, and individual event pages so you can monitor prices, liquidity, volume, and market context without manual browsing.

Use it for active market discovery, resolved market research, category tracking, event-level analysis, dashboards, alerts, and downstream modeling.

What You Can Scrape

• Search queries such as bitcoin, US election, or NBA Finals
• Polymarket search URLs such as https://polymarket.com/?_q=bitcoin
• Topic and category URLs such as https://polymarket.com/predictions/iran, https://polymarket.com/crypto, https://polymarket.com/politics, or https://polymarket.com/sports/live
• Event URLs such as https://polymarket.com/event/when-will-bitcoin-hit-150k

Search and category runs save one record per active or resolved market, depending on your status filter. Exact topic queries and /predictions/... URLs use Polymarket's topic feed first; if a query does not match a topic feed, the actor falls back to keyword search. Event URL runs also include a recent trade snapshot when Polymarket provides it. If multiple inputs discover the same market in one run, the actor saves it once so the dataset stays clean and pay-per-event charging does not double-count the same market.

Input Parameters

Parameter	Type	Description	Default
startUrls	array of strings	Polymarket search, category, sports category, or event URLs to scrape.	-
queries	array of strings	Search phrases used to discover matching Polymarket events and markets.	-
status	string	Market lifecycle filter: active or resolved.	active
sortBy	string	Sort order for discovery: volume_24hr, volume, liquidity, start_date, ending_soon, or competitive.	volume_24hr
frequency	string	Volume window for volume-based sorting: all, daily, weekly, or monthly.	all
limit	integer	Maximum number of market records to save.	50000
proxyConfiguration	object	Connection settings. Apify Residential proxy is preselected for stable runs.	Apify Residential proxy

Example Inputs

Search by query:

{
  "queries": ["bitcoin"],
  "status": "active",
  "sortBy": "volume_24hr",
  "frequency": "daily",
  "limit": 100
}

Scrape a category URL:

{
  "startUrls": ["https://polymarket.com/crypto"],
  "status": "active",
  "sortBy": "volume_24hr",
  "frequency": "daily",
  "limit": 100
}

Scrape an event URL:

{
  "startUrls": ["https://polymarket.com/event/when-will-bitcoin-hit-150k"],
  "limit": 100
}

Example Output

{
  "source": "polymarket",
  "record_type": "market",
  "market_id": "573655",
  "event_id": "36173",
  "url": "https://polymarket.com/event/when-will-bitcoin-hit-150k",
  "question": "Will Bitcoin hit $150k by June 30, 2026?",
  "event_title": "When will Bitcoin hit $150k?",
  "market_status": "active",
  "source_context": {
    "seed_type": "search_query",
    "seed_value": "bitcoin",
    "search_query": "bitcoin",
    "input_type": "search",
    "page_index": 1,
    "status_filter": "active"
  },
  "event": {
    "id": "36173",
    "title": "When will Bitcoin hit $150k?",
    "slug": "when-will-bitcoin-hit-150k",
    "description": "When will Bitcoin hit $150k",
    "timestamps": {
      "start_date": "2025-08-07T16:32:57.401533Z",
      "updated_at": "2026-05-19T21:36:11.190006Z"
    },
    "metrics": {
      "volume": 18360481.244939998,
      "open_interest": 560747.9081219999,
      "liquidity": 49842.41715,
      "volume_24h": 5821943.554085
    },
    "flags": {
      "active": true,
      "closed": false
    },
    "tags": [
      {
        "id": "235",
        "label": "Bitcoin",
        "slug": "bitcoin"
      },
      {
        "id": "21",
        "label": "Crypto",
        "slug": "crypto"
      }
    ]
  },
  "market": {
    "id": "573655",
    "question": "Will Bitcoin hit $150k by June 30, 2026?",
    "slug": "will-bitcoin-hit-150k-by-june-30-2026",
    "condition_id": "0xa0f4c4924ea1a8b410b4ce821c2a9955fad21a1b19bdcfde90816732278b3dd5",
    "outcomes": [
      {
        "name": "Yes",
        "price": 0.0135
      },
      {
        "name": "No",
        "price": 0.9865
      }
    ],
    "pricing": {
      "last_trade_price": 0.014,
      "best_ask": 0.014,
      "best_bid": 0.013,
      "favorite_outcome": "No",
      "favorite_price": 0.9865,
      "spread": 0.001
    },
    "timestamps": {
      "start_date": "2025-08-07T16:29:22.979697Z",
      "end_date": "2026-07-01T04:00:00Z"
    },
    "metrics": {
      "volume": 15734008.014241
    },
    "flags": {
      "active": true,
      "closed": false
    },
    "rules": {
      "description": "This market resolves based on whether the specified Bitcoin price threshold is reached before the listed deadline."
    }
  }
}

Event URL records use the same market shape and include trade_history when recent trade data is available.

Output Notes

• source identifies the platform. The input path is stored in source_context.input_type.
• source_context contains provenance such as seed type, seed value, page index, category, search query, and status filter.
• url is the usable Polymarket event URL for the market record.
• event contains event-level metadata, timestamps, media, metrics, flags, tags, and source-specific attributes.
• market contains market-level IDs, question text, outcomes, pricing, timestamps, metrics, flags, rules, resolution data, trading settings, and source-specific attributes.
• market.outcomes pairs each outcome name with its current price for easier downstream use.
• Duplicate market IDs are skipped within a run, even when multiple inputs overlap.
• Debug, retry, and diagnostic information is not mixed into the default dataset.

Notes & Limitations

• Polymarket data changes quickly; repeated runs can produce different prices, volumes, or trade history.
• Event pages can contain fewer markets than your requested limit.
• Trade snapshots are best-effort and only included for event URL inputs.
• Review Polymarket's terms of service and applicable local rules before redistributing or commercializing data.

Support

Questions or custom needs? Open an issue on the actor page in Apify Console.