Load Klaviyo data to DuckDB

Klaviyo is a marketing automation platform offering APIs for managing customer data, campaigns, and events. Everything needed to build a working Klaviyo → 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 Klaviyo to DuckDB pipeline

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

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Klaviyo 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 Klaviyo 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.

---

Klaviyo API at a glance

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

---

How do I authenticate with the Klaviyo API?

Private key authentication requires an 'Authorization' header with the format 'Klaviyo-API-Key your-private-api-key'.

1. Get your credentials

To obtain a Klaviyo private API key, you must have an Owner or Admin role. Navigate to your account settings by clicking your organization name in the lower left corner and selecting 'Settings'. From there, click on the 'API keys' tab. In the 'Private API Keys' section, select 'Create Private API Key', provide a name, and configure the necessary scopes (e.g., Read-only or Full access). Once created, ensure you copy the key immediately, as it cannot be viewed again once you leave the page. Keep this key secure as it functions like a password.

2. Add them to .dlt/secrets.toml

Copy
[sources.klaviyo_source]
api_key = "pk_live_..."

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 Klaviyo data can I load into DuckDB?

These are the Klaviyo endpoints dlt can load into DuckDB:

---

How do I load only new Klaviyo records?

Klaviyo exposes updated on api/lists, 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.

Copy
{"name": "lists", "endpoint": {
    "path": "api/lists",
    "data_selector": "data",
    "incremental": {"cursor_path": "updated", "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 Klaviyo pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /api/campaigns/ and /api/profiles/ from the Klaviyo API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def klaviyo_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://a.klaviyo.com",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "lists", "endpoint": {"path": "api/lists", "data_selector": "data"}},
            {"name": "campaigns", "endpoint": {"path": "api/campaigns", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_klaviyo_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="klaviyo_pipeline",
        destination="duckdb",
        dataset_name="klaviyo_data",
    )
    load_info = pipeline.run(klaviyo_source())
    print(load_info)


if __name__ == "__main__":
    load_klaviyo_to_duckdb()

Run it with python klaviyo_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 Klaviyo 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):

Copy
import dlt

data = dlt.pipeline("klaviyo_pipeline").dataset()
df = data.lists.df()
print(df.head())

SQL:

Copy
SELECT * FROM klaviyo_data.lists LIMIT 10;

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

---

How do I deploy the Klaviyo 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 Klaviyo 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 Klaviyo data to?

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

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack