No logo available for HeyGen to DuckDB connector icon

Load HeyGen data to DuckDB

Build a HeyGen to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the HeyGen API base URL, auth, endpoints, and incremental loading.

SourceHeyGenHeyGen API DocumentationDestinationDuckDBIn-process analytical database. The default local destination for dlt pipelines.

HeyGen is an AI video generation platform providing an API for programmatic avatar video creation, translation, and streaming. Everything needed to build a working HeyGen → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.


Build your HeyGen to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

Prompt
Run uvx dlthub-init@latest to build a pipeline from HeyGen to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the HeyGen API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.


HeyGen API at a glance

Base URLhttps://api.heygen.com
Example endpointGET v3/videos
Records found atdata
Authenticationall requests require an API key in the X-Api-Key header — sent in the X-Api-Key header
PaginationCursor-based via token, page size via limit. The API uses cursor-based pagination. The cursor for the next page is provided in the response body as 'next_token', which is then passed as the 'token' query parameter in subsequent requests. 'has_more' indicates if further pages exist. The limit parameter determines items per page, with a typical maximum of 100.
Incremental fieldnext_token
API referencehttps://developers.heygen.com/docs/api-key

These values come from the HeyGen API reference — the authoritative source if anything here looks out of date.


How do I authenticate with the HeyGen API?

All HeyGen API requests require the X-Api-Key header containing your API key. Obtain your key from the HeyGen API dashboard.

1. Get your credentials

  1. Navigate to the HeyGen API dashboard at https://app.heygen.com/settings?nav=API. 2. Locate the section to create a new API key. 3. Click to generate the key. Note that the key is displayed only once upon creation, so ensure it is stored securely.

2. Add them to .dlt/secrets.toml

[sources.heygen_source] heygen_api_key = "your_api_key_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.


What HeyGen data can I load into DuckDB?

These are the HeyGen endpoints dlt can load into DuckDB:

ResourceEndpointMethodData selectorDescription
videos/v3/videosGETdataReturns a paginated list of all videos in the account.
video_agent_sessions/v3/video-agentsGETdataReturns a paginated list of video agent sessions.
avatars/v3/avatarsGETdataLists all available avatars.
voices/v3/voicesGETdataLists all available voices.
users/v3/users/meGETRetrieves authenticated user details.

How do I load only new HeyGen records?

HeyGen exposes next_token on v3/videos, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

{"name": "videos", "endpoint": { "path": "v3/videos", "data_selector": "data", "incremental": {"cursor_path": "next_token", "initial_value": "2024-01-01T00:00:00Z"}, }}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.


What does the generated HeyGen pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading GET /v3/videos and POST /v3/videos from the HeyGen API into DuckDB:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def heygen_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.heygen.com", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key", "location": "header"}, }, "resources": [ {"name": "videos", "endpoint": {"path": "v3/videos", "data_selector": "data"}}, {"name": "video_agent_sessions", "endpoint": {"path": "v3/video-agents", "data_selector": "data"}} ], } yield from rest_api_resources(config) def load_heygen_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="heygen_pipeline", destination="duckdb", dataset_name="heygen_data", ) load_info = pipeline.run(heygen_source()) print(load_info) if __name__ == "__main__": load_heygen_to_duckdb()

Run it with python heygen_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.


How do I query HeyGen data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("heygen_pipeline").dataset() df = data.videos.df() print(df.head())

SQL:

SELECT * FROM heygen_data.videos LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.


How do I deploy the HeyGen to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

  • Deploy & schedule — run the pipeline as a managed job with automatic retries.
  • Monitor — observable job queues, alerting, and load metrics for every run.
  • Transform — promote raw HeyGen loads into governed, documented models.
  • Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →


What other destinations can I load HeyGen data to?

dlt loads into any of these — only the destination argument changes:

DestinationExample value
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.


Next steps

Was this page helpful?

Community Hub

Need more dlt context for HeyGen to DuckDB?

Request dlt skills, commands, AGENT.md files, and AI-native context.