Delighted Python API Docs | dltHub
Build a Delighted-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Delighted is a customer feedback and survey platform that provides a REST API for sending surveys, retrieving responses, and managing people. The REST API base URL is https://api.delighted.com/v1 and All requests use HTTP Basic Auth with the API key as the username and a blank password..
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 Delighted data in under 10 minutes.
What data can I load from Delighted?
Here are some of the endpoints you can load from Delighted:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
survey_responses | /v1/survey_responses.json | GET | List of survey response objects. | |
people | /v1/people.json | GET | List of active people objects. | |
metrics | /v1/metrics.json | GET | Metrics summary object. | |
unsubscribed_people | /v1/unsubscribe_people.json | GET | List of people who have unsubscribed. | |
bounced_people | /v1/bounced_people.json | GET | List of people whose emails bounced. |
How do I authenticate with the Delighted API?
The API uses HTTP Basic authentication. Include an Authorization header with the API key as the username and an empty password, e.g., Authorization: Basic base64(api_key:).
1. Get your credentials
- Log in to your Delighted account.
- Click your avatar in the top right corner and select Integrations.
- Choose API from the integrations list.
- Copy the API key shown for your project.
- Store the key securely; it will be used as the HTTP Basic username.
2. Add them to .dlt/secrets.toml
[sources.delighted_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 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 Delighted 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 delighted_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline delighted_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset delighted_data The duckdb destination used duckdb:/delighted.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline delighted_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 survey_responses and people from the Delighted 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 delighted_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.delighted.com/v1", "auth": { "type": "http_basic", "username": api_key, }, }, "resources": [ {"name": "survey_responses", "endpoint": {"path": "survey_responses.json"}}, {"name": "people", "endpoint": {"path": "people.json"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="delighted_pipeline", destination="duckdb", dataset_name="delighted_data", ) load_info = pipeline.run(delighted_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("delighted_pipeline").dataset() sessions_df = data.survey_responses.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM delighted_data.survey_responses LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("delighted_pipeline").dataset() data.survey_responses.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 Delighted 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 failures
- 401 Unauthorized – Returned when the API key is missing or invalid. Verify that the API key is supplied as the HTTP Basic username and that the password is empty.
Rate limiting
- 429 Too Many Requests – The API enforces a rate limit. The response includes a Retry-After header indicating how many seconds to wait before retrying.
Pagination
- List endpoints support
pageandper_pagequery parameters.per_pagedefaults to 20 and can be set up to 100. Responses are returned as a top‑level array; iterate through pages until an empty array is returned.
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 Delighted?
Request dlt skills, commands, AGENT.md files, and AI-native context.