Kalshi Python API Docs | dltHub
Build a Kalshi-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Kalshi's API is a RESTful service for accessing market data and executing trades. To use it, generate API keys and sign requests with a private key. Test in the demo environment first. The REST API base URL is https://api.elections.kalshi.com/trade-api/v2 and All authenticated requests require a Key ID and signed request using your private key (headers: KALSHI-ACCESS-KEY, KALSHI-ACCESS-TIMESTAMP, KALSHI-ACCESS-SIGNATURE)..
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 pip install "dlt[workspace]" and start loading Kalshi data in under 10 minutes.
What data can I load from Kalshi?
Here are some of the endpoints you can load from Kalshi:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| markets | trade-api/v2/markets | GET | markets | Browse available markets (supports filters like series_ticker, status) |
| series | trade-api/v2/series/{ticker} | GET | series | Get metadata for a series (title, frequency, category) |
| events | trade-api/v2/events | GET | events | List events (supports filters) |
| market_orderbook | trade-api/v2/markets/{market_ticker}/orderbook | GET | orderbook | Get orderbook for a market (orderbook.yes / orderbook.no arrays) |
| portfolio_positions | trade-api/v2/portfolio/positions | GET | positions | Get authenticated user's portfolio positions |
How do I authenticate with the Kalshi API?
Kalshi uses API keys where each Key ID (KALSHI-ACCESS-KEY) is paired with a private key used to sign requests. Each request must include the timestamp (ms) and a signature (PSS signing) of timestamp + HTTP_METHOD + request_path in the KALSHI-ACCESS-SIGNATURE header.
1. Get your credentials
- Go to Account Settings (Developer/API Keys) in the Kalshi dashboard. 2) Click Generate New API Key to create a Key ID and download the private key (PEM). 3) Store the Key ID and the private key securely; the private key is used to sign requests and is not stored by Kalshi.
2. Add them to .dlt/secrets.toml
[sources.kalshi_source] api_key = "your_key_id_here" private_key = "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----"
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 Kalshi 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:
python kalshi_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline kalshi_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset kalshi_data The duckdb destination used duckdb:/kalshi.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline kalshi_pipeline 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 markets and series from the Kalshi 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 kalshi_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.elections.kalshi.com/trade-api/v2", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "markets", "endpoint": {"path": "markets", "data_selector": "markets"}}, {"name": "series", "endpoint": {"path": "series/{ticker}", "data_selector": "series"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="kalshi_pipeline", destination="duckdb", dataset_name="kalshi_data", ) load_info = pipeline.run(kalshi_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("kalshi_pipeline").dataset() sessions_df = data.markets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM kalshi_data.markets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("kalshi_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 Kalshi 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 Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Kalshi?
Request dlt skills, commands, AGENT.md files, and AI-native context.