Polymarket Markets & Events Scraper avatar

Polymarket Markets & Events Scraper

Pricing

from $0.60 / 1,000 item processeds

Go to Apify Store
Polymarket Markets & Events Scraper

Polymarket Markets & Events Scraper

Export public Polymarket markets, outcome prices, volume, liquidity, tags, and event context. Filter records and download CSV, Excel, or JSON, or use the API.

Pricing

from $0.60 / 1,000 item processeds

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 days ago

Last modified

Security

Limited permissions

Share

Export public Polymarket markets and event context as structured JSON, CSV, or Excel. Collect questions, outcome prices, volume, liquidity, dates, categories, and tags for research or a downstream data pipeline.

This is a snapshot exporter, not a trading bot, price-history service, or recommendation engine. One dataset row represents one market. Event fields describe its first associated event.

Quick start

Start with the small input below, run the Actor and inspect its results.

{
"status": "active",
"maxItems": 10,
"sortBy": "volume",
"includeRaw": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

  • Market identifiers, question, description, public URL, and status.
  • Outcome names, quoted prices, and public token identifiers.
  • Volume, 24-hour volume, and liquidity when supplied.
  • Associated event context, dates, categories, tags, and resolution-source text.

Who is it for?

  • Public-market researchers retaining dated prediction-market observations.
  • Data engineers importing source-linked markets and nested outcomes.
  • News and event analysts reviewing question wording and associated event context.
  • Research-tool developers comparing their own stored snapshots without trading automation.

How you can use the data

  • Inspect a small active-market snapshot. Use the existing active status, ten-market cap and volume sample sort with raw output off. Keep marketId, question, source URL and fetchedAt beside quoted outcomes rather than treating prices as facts or recommendations.
  • Keep event context distinct from a market. A row represents one market and describes its first associated event. Retain eventId and marketId separately so a multi-market event is not mistaken for one result or complete event history.
  • Refine a sample after inspecting coverage. Add a text or category/tag filter one at a time. Matches apply within the limited collected sample, not the full catalog, and event-title matching is not an exact category-ID filter.
  • Compare retained snapshots in your own destination. Join marketId with collection time, volume, liquidity and outcome names. Preserve nulls and source outcome order. The Actor does not maintain historical prices, make predictions, track wallets or execute trades.

Input settings

Start with a small unfiltered sample. Paste this JSON into the Actor input, run it, then open the dataset to inspect and export the results.

{
"status": "active",
"maxItems": 10,
"sortBy": "volume",
"includeRaw": false
}

More input settings

SettingJSON keyType / defaultWhat it does
Search queryquerystring / not setOptional text to match in market question, slug, description, or event title.
Market statusstatusstring / "active"Which markets to fetch. Values: active, closed, all.
Maximum marketsmaxItemsinteger / 25Maximum number of market records to save. Minimum 1. Maximum 10000.
Sort bysortBystring / "volume"Sort the collected sample, not the full Polymarket catalog: volume, liquidity, newest, or closingSoon. Values: volume, liquidity, newest, closingSoon.
Category or tagcategoryOrTagstring / not setOptional category/tag filter.
Minimum volumeminVolumenumber / not setOnly keep markets with at least this volume. Minimum 0.
Minimum liquidityminLiquiditynumber / not setOnly keep markets with at least this liquidity. Minimum 0.
Include raw API responseincludeRawboolean / falseInclude the raw Polymarket API object on each dataset item.

Output data

Illustrative, shortened record—not live market data. Actual records include all fields listed below.

{
"marketId": "example-market",
"question": "Example market question?",
"status": "active",
"outcomes": [
{
"name": "Yes",
"price": 0.6,
"tokenId": null
},
{
"name": "No",
"price": 0.4,
"tokenId": null
}
],
"bestOutcome": "Yes",
"volume": 12500,
"liquidity": 3500,
"eventTitle": "Example event",
"category": null,
"tags": [],
"fetchedAt": "2026-08-31T00:00:00.000Z"
}

More output fields

JSON keyTypeMeaning
marketIdstringPublic market identifier.
conditionIdstring / nullMarket condition identifier when supplied.
questionstringPublic market question or title.
slugstring / nullHuman-readable market identifier when supplied.
urlstring / nullPublic market URL assembled from event and market slugs.
eventIdstring / nullIdentifier of the first associated event, when available.
eventTitlestring / nullTitle of the first associated event, when available.
eventSlugstring / nullSlug of the first associated event, when available.
activeboolean / nullSource active flag. Null means unavailable.
closedboolean / nullSource closed flag. Null means unavailable.
statusstringDerived status: closed, active, archived, or inactive.
outcomesarrayOutcomes aligned with their quoted prices and token identifiers.
outcomePricesarrayQuoted prices in source outcome order.
bestOutcomestring / nullName of the highest-priced available outcome. Not a trading recommendation.
volumenumber / nullMarket volume reported by the source, not computed by this Actor.
volume24hrnumber / nullTrailing-24-hour volume when supplied by the source.
liquiditynumber / nullMarket liquidity reported by the source.
startDatestring / nullSource start date when available.
endDatestring / nullSource closing date when available. Not a guaranteed resolution date.
categorystring / nullMarket category or first-event category when supplied.
tagsarrayDistinct tags from the market and its associated events.
clobTokenIdsarrayPublic CLOB token identifiers in source order.
descriptionstring / nullPublic market description when available.
resolutionSourcestring / nullPublic resolution-source text when supplied.
fetchedAtstringUTC timestamp when this market record was collected.
sourcestringPublic data-source URL.
rawobjectUnmodified source market object. Included only when includeRaw is true.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged when the run begins, including a run without matching markets. The item event applies to each saved market row. The run summary is not a market result.

Use a small explicit cap and see the live Pricing tab for current rates and discounts. Apify reports any applicable platform usage separately.

Tips for best results

  • Begin with a small unfiltered active sample. Add text or category refinements after reviewing returned records.
  • Keep outcome names aligned with quoted prices. Highest quoted price is not a recommendation or verified outcome.
  • Retain market and event identifiers separately. A row is one market with first-event context.
  • Read the source record cap before claiming rankings. Sort order applies to the collected sample.
  • Keep dated exports for your own monitoring. Scheduled collection does not itself compute changes.

Limits and caveats

This is an independent public-data exporter without Polymarket login or wallet access. It does not provide order books, wallet positions, trade execution, recommendations, predictions or a historical-price service. Source availability and quoted values can change.

Query is a case-insensitive text match over question, slug, description and event context. CategoryOrTag matches categories, tags and event title or slug rather than an exact category ID. The current collection considers at most twenty-five hundred source records per open or closed group, so restrictive filters or a large cap can return fewer results than requested.

SortBy orders the filtered collected sample, not every market in Polymarket. It does not guarantee the global highest volume or soonest closing markets. With all status selected, open markets are considered before closed markets and a small cap can fill before reaching closed records.

Each row is a market with its first associated event. Missing numeric and text values are null and missing arrays empty. BestOutcome names the highest available quoted-price outcome rather than a prediction or recommendation. Closing date is source metadata rather than a guaranteed resolution date.

A valid zero-match sample can occur within these collection limits. Inspect RUN-SUMMARY saved counts, pages checked and applied inputs rather than treating no rows as proof a market does not exist. Schedule repeated collection and compare market IDs in your own destination if you need change analysis.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~polymarket-markets-events-scraper/runs' \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
--data @- <<'JSON'
{
"status": "active",
"maxItems": 10,
"sortBy": "volume",
"includeRaw": false
}
JSON

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/polymarket-markets-events-scraper').call({
"status": "active",
"maxItems": 10,
"sortBy": "volume",
"includeRaw": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/polymarket-markets-events-scraper').call(run_input={'status': 'active', 'maxItems': 10, 'sortBy': 'volume', 'includeRaw': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

Save the quickstart JSON as input.json. This request starts a run asynchronously. Use its returned run ID to check completion and its defaultDatasetId to retrieve results.

MCP and AI agents

You can ask your AI assistant to collect data with Polymarket Markets & Events Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Polymarket Markets & Events Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/polymarket-markets-events-scraper"
}
}
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Polymarket Markets & Events Scraper by Fetch Cat, or give it the identifier fetch_cat/polymarket-markets-events-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Use Fetch Cat’s Polymarket Markets and Events Scraper to collect up to 5 active markets with volume ordering and raw output off. Keep source links, question wording and quoted outcome prices, without recommending trades or calling it a global volume ranking.”
  • “Collect up to 5 active Polymarket markets with liquidity ordering and raw output off. Keep market and first-associated-event identifiers separate, with collection times and null values intact.”
  • “Retrieve up to 5 Polymarket market records with all statuses, newest ordering and raw output off. Note that open records are considered first and keep IDs for comparison with my own stored snapshots, without claiming price history.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it return live trading signals?

No. It returns public market records observed during collection. Quoted prices are not guarantees or recommendations.

Why did my query return no markets?

It may have no match inside the bounded collected sample. Test without text/category filters and inspect RUN-SUMMARY. Do not interpret an empty dataset as proof that the market does not exist.

Does it require a Polymarket account?

No Polymarket login or wallet is used for this public-data export. Calling the Actor through Apify API still requires your Apify token.

Can I export to CSV or call an API?

Yes. Use the dataset export controls or Apify Dataset API. JSON retains nested outcomes. Choose and flatten fields as needed for a spreadsheet.

  • CoinMarketCap Crypto Prices Scraper — Collect public cryptocurrency price, market-cap and trading-volume snapshots from CoinMarketCap.
  • Google Trends Scraper — Collect current country-level Trending Now topics, traffic labels and news context, without historical keyword-interest data.
  • Google News Scraper — Collect public Google News feed headlines, dates and links.
  • Reddit Scraper — Collect public Reddit posts and optional comments from supported feeds, searches or discussion URLs.
  • X / Twitter Posts Scraper — Collect public X post text, author details and available engagement from supplied public profile or post URLs.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥