# Polymarket Markets & Events Scraper (`literate_universe/polymarket-markets-scraper`) Actor

Extract live Polymarket prediction markets: election odds, politics, crypto, sports and culture. Questions, outcomes, YES/NO prices, bid/ask, spread, volume, liquidity and end dates. Filter by keyword, volume or status. Public API, no wallet or login.

- **URL**: https://apify.com/literate\_universe/polymarket-markets-scraper.md
- **Developed by:** [John Rutherford](https://apify.com/literate_universe) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 market rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Polymarket Markets & Events Scraper

Pull **live Polymarket prediction-market data** into a clean dataset: every question, its outcomes and prices, bid/ask and spread, volume, liquidity, end date and parent event. No wallet, no login, no API key.

Use it to monitor odds on politics, crypto, sports and culture; to feed dashboards, alerts or research; or to export Polymarket to CSV / Excel / JSON in one click.

### What you get

One row per market:

| Field | Meaning |
|---|---|
| `question`, `slug`, `url` | The market and its page |
| `event_title`, `event_slug`, `event_id` | The parent event that groups related markets |
| `outcomes`, `outcome_prices` | Outcome labels and current prices (0 to 1) |
| `yes_price`, `no_price` | Filled for Yes/No markets |
| `best_bid`, `best_ask`, `spread`, `last_trade_price` | Order book top |
| `volume`, `volume_24h`, `liquidity` | Activity in USD |
| `start_date`, `end_date`, `active`, `closed` | Timing and status |
| `resolution_source`, `condition_id`, `image` | Extras |

Sample row:

```json
{
  "question": "Will the price of Bitcoin be above $76,000 on September 11?",
  "event_title": "Bitcoin price on September 11?",
  "yes_price": 0.887,
  "best_bid": 0.88,
  "best_ask": 0.89,
  "volume_24h": 412903.5,
  "liquidity": 98210.2,
  "end_date": "2026-09-11T16:00:00Z",
  "url": "https://polymarket.com/event/bitcoin-price-on-september-11"
}
```

### Input

| Option | Default | What it does |
|---|---|---|
| **Market status** | active | Active, closed, or all |
| **Keyword filter** | | Keep only questions containing this text |
| **Min 24h volume / Min liquidity** | 0 | Skip thin markets |
| **Order by** | 24h volume | Scan order, descending |
| **Yes/No markets only** | off | Skip multi-outcome markets |
| **Max markets** | 500 | Cap output |

### Pricing

Pay per event: one small charge per market row. Filtering happens before charging.

### Notes and limits

- Reads Polymarket's public Gamma API. Prices are the current market prices at scrape time.
- Multi-outcome markets (two teams, several candidates) list all outcomes in `outcomes` with matching `outcome_prices`.
- This Actor never places orders.

### Related

- Polymarket vs Kalshi Matched Markets: the same question on both venues with the price gap.
- Kalshi Markets Scraper: every Kalshi market with prices, volume and order books.

# Actor input Schema

## `status` (type: `string`):

Active (open for trading), closed (resolved or expired), or all.

## `searchQuery` (type: `string`):

Keep only markets whose question or event title contains this text (case-insensitive).

## `minVolume24h` (type: `number`):

Skip markets with less 24-hour volume than this.

## `minLiquidity` (type: `number`):

Skip markets with less liquidity than this.

## `orderBy` (type: `string`):

Sort order of the scan (descending).

## `yesNoOnly` (type: `boolean`):

Skip multi-outcome markets (for example two-team matchups) and keep only Yes/No questions.

## `maxItems` (type: `integer`):

Stop after this many markets.

## Actor input object example

```json
{
  "status": "active",
  "minVolume24h": 0,
  "minLiquidity": 0,
  "orderBy": "volume24hr",
  "yesNoOnly": false,
  "maxItems": 500
}
```

# Actor output Schema

## `markets` (type: `string`):

All market rows as JSON. Append ?format=csv for CSV.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("literate_universe/polymarket-markets-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("literate_universe/polymarket-markets-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call literate_universe/polymarket-markets-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,literate_universe/polymarket-markets-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/B2iBNrDb32eKMw7Yp/builds/xDRvnH1FWxW0ZJcdi/openapi.json