Vonage Python API Docs | dltHub

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

Last updated:

Vonage is a communications platform providing APIs for voice, messaging, verification, and network services. The REST API base URL is https://api.nexmo.com/ or https://api.vonage.com/ (product-dependent) and Requests require either an Authorization header with Basic auth or a Bearer token..

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 Vonage data in under 10 minutes.


What data can I load from Vonage?

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

ResourceEndpointMethodData selectorDescription
conversations/v1/conversationsGET_embedded.conversationsList all conversations
applications/v2/applicationsGET_embedded.applicationsList all applications
inbound_numbers/account/numbersGETnumbersList owned inbound numbers
available_numbers/number/searchGETnumbersSearch available inbound numbers
sync_reports/v2/reportsGETRetrieve records synchronously (batch)

How do I authenticate with the Vonage API?

Vonage APIs use either Basic Authentication (API key and secret Base64 encoded) or JWT Bearer authentication. Both require an Authorization header: 'Authorization: Basic <base64(api_key

)>' or 'Authorization: Bearer <jwt_token>'.

1. Get your credentials

  1. Log in to the Vonage Dashboard (https://dashboard.nexmo.com/).\n2. Navigate to the 'Settings' section from the left sidebar.\n3. Click on 'API Settings'.\n4. Your 'API Key' will be visible on the page. \n5. Your 'API Secret' can be found in the 'API Key Secret' section. If not visible, you may need to click 'Show' or create a new secret if you haven't saved one previously (note that secrets are often masked or no longer displayed in the dashboard after initial creation/account setup for security). Ensure you save these credentials securely in a secrets manager or environment variables.

2. Add them to .dlt/secrets.toml

[sources.vonage_source] api_key, api_secret, or jwt_token = "REPLACE_ME"

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 Vonage 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 vonage_pipeline.py

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

Pipeline vonage_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset vonage_data The duckdb destination used duckdb:/vonage.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 '/v2/reports/records' and '/t/vbc.prod/vis/v1/self/calls' from the Vonage 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 vonage_source(api_key_api_secret_or_jwt_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.nexmo.com/ or https://api.vonage.com/ (product-dependent)", "auth": {"type": "bearer", "token": api_key_api_secret_or_jwt_token}, }, "resources": [ {"name": "conversations", "endpoint": {"path": "v1/conversations", "data_selector": "_embedded.conversations"}}, {"name": "applications", "endpoint": {"path": "v2/applications", "data_selector": "_embedded.applications"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="vonage_pipeline", destination="duckdb", dataset_name="vonage_data", ) load_info = pipeline.run(vonage_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("vonage_pipeline").dataset() sessions_df = data.conversations.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM vonage_data.conversations LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("vonage_pipeline").dataset() data.conversations.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 Vonage 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 Vonage?

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