Goldcast Python API Docs | dltHub
Build a Goldcast-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Goldcast is an all-in-one virtual event platform that provides REST APIs to programmatically create, manage, and retrieve event, agenda, attendee, and related resources. The REST API base URL is https://customapi.goldcast.io and All requests require a Goldcast personal access token (Bearer token) provided in the Authorization 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 Goldcast data in under 10 minutes.
What data can I load from Goldcast?
Here are some of the endpoints you can load from Goldcast:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| organization | /core/organization/ | GET | results | List organizations |
| events | /event/ | GET | results | List events (paginated) |
| event_public_list | /event/public/v1/list/ | GET | results | Public events list |
| agenda_items | /event/agenda-item/ | GET | results | List agenda items |
| booths | /event/booths/ | GET | results | List booths |
| broadcasts | /event/broadcasts/ | GET | results | List broadcasts |
| event_members | /event/event-members/ | GET | results | List event members |
| resources | /event/resources/ | GET | results | List event resources |
| get_session_attendance | /event/get_session_attendance/ | GET | Retrieve session attendance (top‑level object) |
How do I authenticate with the Goldcast API?
Goldcast uses personal API tokens (personal access tokens). Include header: Authorization: Bearer {TOKEN}. Tokens must be generated in Goldcast Studio (Tokens settings) and are shown only once when created.
1. Get your credentials
- Login to Goldcast Studio (https://admin.goldcast.io/auth/login). 2) Go to Settings -> Tokens. 3) Click Create New Token, name it and Generate Token. 4) Copy the token value immediately; it is only displayed once. Note: tokens are disabled by default and must be enabled by contacting Goldcast Support if not available in your plan.
2. Add them to .dlt/secrets.toml
[sources.goldcast_source] token = "your_goldcast_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 Goldcast 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 goldcast_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline goldcast_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset goldcast_data The duckdb destination used duckdb:/goldcast.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline goldcast_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 event_members from the Goldcast 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 goldcast_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://customapi.goldcast.io", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "events", "endpoint": {"path": "event/", "data_selector": "results"}}, {"name": "event_members", "endpoint": {"path": "event/event-members/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="goldcast_pipeline", destination="duckdb", dataset_name="goldcast_data", ) load_info = pipeline.run(goldcast_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("goldcast_pipeline").dataset() sessions_df = data.events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM goldcast_data.events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("goldcast_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 Goldcast 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 failures
If you receive 401 Unauthorized, verify that the Authorization header is present and formatted as Bearer {TOKEN}. Ensure the token was copied when created; tokens are shown only once. If tokens are disabled for your organization, contact Goldcast Support.
Pagination and data selectors
List endpoints return a paginated object containing a results array along with count, next, and previous fields. Use the results key as the data selector when iterating records.
Rate limits and other errors
Goldcast does not publish explicit rate‑limit values. For 429 Too Many Requests, implement exponential back‑off and retry. For 403 Forbidden, check token scope and organization permissions.
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 Goldcast?
Request dlt skills, commands, AGENT.md files, and AI-native context.