Load Livevox data to DuckDB

LiveVox is a cloud contact center platform providing REST APIs to manage accounts, campaigns, contacts, sessions, queues, and reporting. Everything needed to build a working Livevox → 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 Livevox 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 Livevox 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 Livevox 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.

---

Livevox API at a glance

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

---

How do I authenticate with the Livevox API?

Authentication requires an 'LV-Access' header (containing an API tracking token) for the initial login request to obtain a session ID. All subsequent requests require an 'LV-Session' header containing the returned session ID.

1. Get your credentials

To obtain API credentials for LiveVox, you must have a configured user with appropriate permissions in the LiveVox Portal (LVP). During the onboarding process, your organization is provided with an API Application Token, which uniquely identifies your client application. If additional tokens are required to track usage per application, you can request them through your account management process (up to 5 tokens). When establishing a login session via the API, you must provide your username, password, and the API Token. Consult your LiveVox account representative or the administrative interface settings for credential management.

2. Add them to .dlt/secrets.toml

Copy
[sources.livevox_source]
livevox_client_code = "YOUR_CLIENT_CODE"
livevox_api_token = "YOUR_API_TOKEN"
livevox_username = "YOUR_USERNAME"
livevox_password = "YOUR_PASSWORD"

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

These are the Livevox endpoints dlt can load into DuckDB:

---

How do I load only new Livevox records?

Livevox exposes offset on contact/contacts, 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": "contacts", "endpoint": {
    "path": "contact/contacts",
    "incremental": {"cursor_path": "offset", "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 Livevox pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading session/login and configuration (or specific resource endpoints like reporting) from the Livevox API into DuckDB:

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

@dlt.source
def livevox_source(lv_access=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.livevox.com/{apiCategory}/{apiResource}",
            "auth": {"type": "api_key", "api_key": lv_access, "name": "lv_access"},
        },
        "resources": [
            {"name": "contacts", "endpoint": {"path": "contact/contacts"}},
            {"name": "accounts", "endpoint": {"path": "account/accounts"}}
        ],
    }
    yield from rest_api_resources(config)


def load_livevox_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="livevox_pipeline",
        destination="duckdb",
        dataset_name="livevox_data",
    )
    load_info = pipeline.run(livevox_source())
    print(load_info)


if __name__ == "__main__":
    load_livevox_to_duckdb()

Run it with python livevox_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 Livevox 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("livevox_pipeline").dataset()
df = data.contacts.df()
print(df.head())

SQL:

Copy
SELECT * FROM livevox_data.contacts LIMIT 10;

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

---

How do I deploy the Livevox 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 Livevox 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 Livevox 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