Whatconverts Python API Docs | dltHub

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

Last updated:

WhatConverts is a call- and lead-tracking platform exposing account, profile, lead, recording and related data via a REST API. The REST API base URL is https://app.whatconverts.com/api/v1/ and All requests require HTTP Basic authentication using an API token and secret..

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 pip install "dlt[workspace]" and start loading Whatconverts data in under 10 minutes.


What data can I load from Whatconverts?

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

ResourceEndpointMethodData selectorDescription
accounts/accountsGETaccountsPaginated list of accounts (agency key required for account access).
accounts_single/accounts/{account_id}GETDetails for a single account.
leads/leadsGETleadsPaginated list of leads; supports many filters (start_date, end_date, leads_per_page, page_number, account_id, profile_id, etc.).
leads_single/leads/{lead_id}GETFull details for a single lead (optionally include customer_journey=true).
recordings/recordingGETReturns MP3 recording for a lead (requires lead_id parameter).
profiles/profilesGETprofilesPaginated list of profiles.
users/usersGETusersPaginated list of users.
roles/rolesGETrolesList of role definitions.
tracking/trackingGETtrackingTracking-related endpoints for configuration and data.

How do I authenticate with the Whatconverts API?

The API uses HTTP Basic auth: supply your API token as the username and API secret as the password (e.g. curl -u token:secret https://app.whatconverts.com/api/v1/leads).

1. Get your credentials

  1. Log in to WhatConverts and navigate to the desired account (required for agency plans).
  2. Select a profile (or the account‑level Integrations → API Keys for agency/master keys).
  3. From the Tracking dropdown open Integrations → API Keys (or Help Center → Generate a Profile API Key).
  4. Click Generate API Key / Add API Key; the page will display the token and secret. Save both; token is used as HTTP Basic username and secret as password.

2. Add them to .dlt/secrets.toml

[sources.whatconverts_source] token = "your_api_token_here" secret = "your_api_secret_here"

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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

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

dlt ai toolkit rest-api-pipeline install

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

python whatconverts_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline whatconverts_pipeline 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 leads and accounts from the Whatconverts 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 whatconverts_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://app.whatconverts.com/api/v1/", "auth": { "type": "http_basic", "token": token, }, }, "resources": [ {"name": "leads", "endpoint": {"path": "leads", "data_selector": "leads"}}, {"name": "accounts", "endpoint": {"path": "accounts", "data_selector": "accounts"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="whatconverts_pipeline", destination="duckdb", dataset_name="whatconverts_data", ) load_info = pipeline.run(whatconverts_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("whatconverts_pipeline").dataset() sessions_df = data.leads.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM whatconverts_data.leads LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("whatconverts_pipeline").dataset() data.leads.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 Whatconverts 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.


Troubleshooting

Authentication failures

If you receive 401 Unauthorized, verify you are using HTTP Basic auth (token as username and secret as password). Ensure you use the correct Profile vs Agency/Master key for the endpoint you are calling (account‑level endpoints require an Agency/Master key).

Rate limits and quotas

Profile keys: up to 1,000 requests/day. Master/Agency keys: up to 10,000 requests/day. The API also permits 1 request/ms and up to 20 concurrent requests by default; contact WhatConverts to request higher limits.

Pagination and large pages

List endpoints are paginated. Use leads_per_page (default 25, max 2500) and page_number to iterate. Responses include page_number, total_pages and total_leads (or total_accounts). For large datasets set leads_per_page to the maximum and paginate until page_number == total_pages.

Recording download quirks

Recordings endpoint (/recording) returns binary MP3 data; do not attempt to parse as JSON — use streaming/binary download.

Common API errors

  • 400 Bad Request: invalid parameters (date format, invalid IDs)
  • 401 Unauthorized: invalid token/secret or insufficient key scope
  • 403 Forbidden: trying to access account‑level resources with a profile key
  • 404 Not Found: resource id does not exist
  • 429 Too Many Requests: excessive concurrent or total request rate (observe per‑key quotas)

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


Next steps

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

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

Was this page helpful?

Community Hub

Need more dlt context for Whatconverts?

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