Livevox Python API Docs | dltHub

Build a Livevox-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

LiveVox is a cloud contact center platform providing REST APIs to manage accounts, campaigns, contacts, sessions, queues, and reporting. The REST API base URL is https://api.livevox.com/{apiCategory}/{apiResource} and all requests require either LV-Access (for login) or LV-Session (for all other requests) header authentication.

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 add "dlt[hub]" and start loading Livevox data in under 10 minutes.


What data can I load from Livevox?

Here are some of the endpoints you can load from Livevox:

ResourceEndpointMethodData selectorDescription
contacts/contact/contactsGETRetrieves a list of contacts
accounts/account/accountsGETRetrieves a list of accounts
campaigns/campaign/campaignsGETRetrieves a list of campaigns
sessions/session/sessionsGETRetrieves a list of active sessions
ticketing/ticketing/ticketsGETRetrieves a list of tickets

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

[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 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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Livevox 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:

uv run python livevox_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline livevox_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset livevox_data The duckdb destination used duckdb:/livevox.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub 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 session/login and configuration (or specific resource endpoints like reporting) from the Livevox 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 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 get_data() -> None: pipeline = dlt.pipeline( pipeline_name="livevox_pipeline", destination="duckdb", dataset_name="livevox_data", ) load_info = pipeline.run(livevox_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("livevox_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM livevox_data.contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("livevox_pipeline").dataset() data.contacts.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 Livevox data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Livevox?

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

Available Pipelines