360dialog Python API Docs | dltHub
Build a 360dialog-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
360dialog is an API that enables the programmatic management of WhatsApp Business Accounts and phone numbers. The REST API base URL is https://hub.360dialog.io/api/v2 and All requests require an API Key for authentication, passed in the 'x-api-key' header for the Partner API or 'D360-API-KEY' for the Cloud API..
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 360dialog data in under 10 minutes.
What data can I load from 360dialog?
Here are some of the endpoints you can load from 360dialog:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| partners | partners | GET | partners | Retrieve a list of partners |
| partner_by_id | partners/{partner-id} | GET | partner | Retrieve a specific partner by ID |
| clients | clients | GET | clients | Retrieve a list of clients |
| client_by_id | clients/{client-id} | GET | client | Retrieve a specific client by ID |
| channels | channels | GET | channels | Retrieve a list of channels |
| channel_by_id | channels/{channel-id} | GET | channel | Retrieve a specific channel by ID |
| webhooks | webhooks | GET | webhooks | Retrieve webhook configurations |
| balance | balance | GET | balance | Retrieve account balance information |
| usage | usage | GET | usage | Retrieve usage statistics |
How do I authenticate with the 360dialog API?
Authentication for the 360dialog API is done using an API Key. For the Partner API, include the API Key in the 'x-api-key' header. For the Cloud API, use the 'D360-API-KEY' header.
1. Get your credentials
The documentation does not provide explicit step-by-step instructions for obtaining API credentials from a dashboard. It states that an API Key is required for authentication.
2. Add them to .dlt/secrets.toml
[sources.api_360dialog_source] api_key = "your_api_key_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 init uv add "dlt[hub]"
1. Install the dlt AI Workbench:
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 360dialog 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 api_360dialog_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline api_360dialog_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset api_360dialog_data The duckdb destination used duckdb:/api_360dialog.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 partners and clients from the 360dialog 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 api_360dialog_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://hub.360dialog.io/api/v2", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "partners", "endpoint": {"path": "partners", "data_selector": "partners"}}, {"name": "clients", "endpoint": {"path": "clients", "data_selector": "clients"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="api_360dialog_pipeline", destination="duckdb", dataset_name="api_360dialog_data", ) load_info = pipeline.run(api_360dialog_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("api_360dialog_pipeline").dataset() sessions_df = data.partners.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM api_360dialog_data.partners LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("api_360dialog_pipeline").dataset() data.partners.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 360dialog data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Errors
If you encounter a 401 Unauthorized error, it indicates that your authentication credentials (API Key) are either invalid or missing from the request.
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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-runtime
Was this page helpful?
Community Hub
Need more dlt context for 360dialog?
Request dlt skills, commands, AGENT.md files, and AI-native context.