Eventbrite Python API Docs | dltHub
Build a Eventbrite-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Eventbrite is an online event management and ticketing platform offering a REST API for accessing events, orders, and related data. The REST API base URL is https://www.eventbriteapi.com/v3 and All Eventbrite API requests must be authenticated with a valid OAuth Bearer token..
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 Eventbrite data in under 10 minutes.
What data can I load from Eventbrite?
Here are some of the endpoints you can load from Eventbrite:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| events | organizations/{organization_id}/events/ | GET | events | List events for a specific organization (paginated). |
| event | events/{event_id}/ | GET | Retrieve details of a single event. | |
| orders | events/{event_id}/orders/ | GET | orders | List orders for a specific event (paginated). |
| order | orders/{order_id}/ | GET | Retrieve details of a single order. | |
| attendees | orders/{order_id}/attendees/ | GET | attendees | List attendees for a specific order. |
How do I authenticate with the Eventbrite API?
Authentication requires sending the OAuth token in the Authorization: Bearer <token> header or as a token query parameter.
1. Get your credentials
- Log into your Eventbrite account and navigate to the developer portal.
- Click Create a New App and fill in the required details.
- After the app is created, open the app settings and choose Show Client Secret and OAuth Token.
- Copy the displayed Anonymous Access OAuth token (or run the OAuth flow using the client ID/secret to generate a token).
- Store this token securely; it will be used as the Bearer token for API requests.
2. Add them to .dlt/secrets.toml
[sources.eventbrite_source] token = "your_oauth_token_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 Eventbrite 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 eventbrite_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline eventbrite_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset eventbrite_data The duckdb destination used duckdb:/eventbrite.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline eventbrite_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 events and orders from the Eventbrite 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 eventbrite_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.eventbriteapi.com/v3", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "events", "endpoint": {"path": "organizations/{organization_id}/events", "data_selector": "events"}}, {"name": "orders", "endpoint": {"path": "events/{event_id}/orders", "data_selector": "orders"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="eventbrite_pipeline", destination="duckdb", dataset_name="eventbrite_data", ) load_info = pipeline.run(eventbrite_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("eventbrite_pipeline").dataset() sessions_df = data.events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM eventbrite_data.events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("eventbrite_pipeline").dataset() data.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 Eventbrite 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
- 401 Unauthorized – Occurs when the Bearer token is missing, malformed, or expired. Verify that the
Authorization: Bearer <token>header is present and the token is still valid.
Rate Limiting
- Eventbrite enforces request quotas. If a 429 Too Many Requests response is received, back‑off for a few seconds and retry.
Pagination
- All list endpoints are paginated in groups of 50 records. Use the
pagequery parameter to request subsequent pages. The response includes apaginationobject withhas_more_itemsandpage_numberfields to guide navigation.
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 Eventbrite?
Request dlt skills, commands, AGENT.md files, and AI-native context.