Luma Python API Docs | dltHub
Build a Luma-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Luma is a scheduling and event management platform that offers a REST API for accessing calendars, events, guests and related resources. The REST API base URL is https://public-api.luma.com and All requests require an API key passed in the x-luma-api-key header..
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 Luma data in under 10 minutes.
What data can I load from Luma?
Here are some of the endpoints you can load from Luma:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| calendar_list_events | /calendar/list-events | GET | events | List all events for a calendar. |
| guest_list_guests | /guest/list-guests | GET | guests | List all guests associated with a calendar. |
| calendar_list_people | /calendar/list-people | GET | people | List people (hosts, organizers) linked to a calendar. |
| webhook_list_webhooks | /webhook/list-webhooks | GET | webhooks | Retrieve configured webhooks. |
| membership_list_membership_tiers | /membership/list-membership-tiers | GET | tiers | List membership tier definitions. |
| event_get | /event/get | GET | Retrieve details of a single event. | |
| guests_get | /guest/get | GET | Retrieve details of a single guest. |
How do I authenticate with the Luma API?
Include the header x-luma-api-key: YOUR_API_KEY on every request. No additional authentication steps are required.
1. Get your credentials
- Log in to the Luma app.
- Go to Calendars Home and select the calendar you want to access.
- Open Settings → Developer.
- In the API Keys section, copy the displayed API key.
- Ensure the calendar has an active Luma Plus subscription, otherwise the key will not work.
2. Add them to .dlt/secrets.toml
[sources.luma_events_source] api_key = "your_api_key_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 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 Luma 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 luma_events_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline luma_events_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset luma_events_data The duckdb destination used duckdb:/luma_events.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline luma_events_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 calendar_list_events and guest_list_guests from the Luma 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 luma_events_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://public-api.luma.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "calendar_list_events", "endpoint": {"path": "calendar/list-events", "data_selector": "events"}}, {"name": "guest_list_guests", "endpoint": {"path": "guest/list-guests", "data_selector": "guests"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="luma_events_pipeline", destination="duckdb", dataset_name="luma_events_data", ) load_info = pipeline.run(luma_events_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("luma_events_pipeline").dataset() sessions_df = data.calendar_list_events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM luma_events_data.calendar_list_events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("luma_events_pipeline").dataset() data.calendar_list_events.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 Luma 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.
Troubleshooting
Authentication Errors
If the x-luma-api-key header is missing or the key is invalid, the API returns a 401 Unauthorized response. Ensure the key is copied from the Developer section of the calendar settings and that the calendar has an active Luma Plus subscription.
Rate Limits
Luma enforces a limit of 300 requests per minute across all endpoints. Exceeding this limit results in a 429 Too Many Requests response and a lockout for one minute. Implement exponential back‑off or request throttling to stay within the limit.
General HTTP Errors
Other 4xx/5xx responses indicate malformed requests or server issues. Review the response body for error codes and messages.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Luma?
Request dlt skills, commands, AGENT.md files, and AI-native context.