Polymarket Gamma Python API Docs | dltHub
Build a Polymarket Gamma-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Polymarket Gamma API provides market discovery, event metadata, and trading data for the Polymarket platform. The REST API base URL is https://gamma-api.polymarket.com and Requests require HMAC-SHA256 signature and five custom headers for L2 authentication..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Polymarket Gamma data in under 10 minutes.
What data can I load from Polymarket Gamma?
Here are some of the endpoints you can load from Polymarket Gamma:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| markets | markets/keyset | GET | List markets with keyset pagination | |
| events | events/keyset | GET | List events with keyset pagination | |
| market_by_slug | markets/slug/{slug} | GET | Get market by slug | |
| markets_list | markets | GET | List markets | |
| events_list | events | GET | List events |
How do I authenticate with the Polymarket Gamma API?
Requests require custom headers (POLY_ADDRESS, POLY_SIGNATURE, POLY_TIMESTAMP, POLY_API_KEY, POLY_PASSPHRASE). The signature is an HMAC-SHA256 hash of the timestamp, HTTP method, path, and request body.
1. Get your credentials
The Gamma API itself is for public market metadata and does not require credentials. For trading operations (CLOB API), you must generate L2 credentials (apiKey, secret, passphrase) using an L1 authentication flow. This involves using your wallet to sign an EIP-712 message (using the 'ClobAuth' domain) to either create or derive the API credentials. Most developers use the official Polymarket SDKs (e.g., Python or TypeScript) to handle this process automatically via methods like create_or_derive_api_key. If implementing the REST API manually, you must send a POST request to https://clob.polymarket.com/auth/api-key with headers containing your address, signature, timestamp, and nonce to receive the credentials in the JSON response.
2. Add them to .dlt/secrets.toml
[sources.polymarket_gamma_source] POLY_API_KEY = "your_api_key_here" POLY_API_SECRET = "your_api_secret_here" POLY_API_PASSPHRASE = "your_api_passphrase_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Polymarket Gamma API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python polymarket_gamma_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline polymarket_gamma_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset polymarket_gamma_data The duckdb destination used duckdb:/polymarket_gamma.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /events and /markets from the Polymarket Gamma API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def polymarket_gamma_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://gamma-api.polymarket.com", "auth": {"type": "api_key", "api_key": api_key, "name": "POLY_API_KEY"}, }, "resources": [ {"name": "events", "endpoint": {"path": "events/keyset", "data_selector": "data"}}, {"name": "markets", "endpoint": {"path": "markets/keyset", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="polymarket_gamma_pipeline", destination="duckdb", dataset_name="polymarket_gamma_data", ) load_info = pipeline.run(polymarket_gamma_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("polymarket_gamma_pipeline").dataset() sessions_df = data.markets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM polymarket_gamma_data.markets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("polymarket_gamma_pipeline").dataset() data.markets.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Polymarket Gamma data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Polymarket Gamma?
Request dlt skills, commands, AGENT.md files, and AI-native context.