Cleverreach Python API Docs | dltHub
Build a Cleverreach-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
CleverReach is an email marketing platform that provides a REST API to manage groups, receivers, mailings, reports, attributes and webhooks. The REST API base URL is https://rest.cleverreach.com and All requests require an OAuth2 access_token (Bearer) — tokens obtained via OAuth2 Authorization Code or Client Credentials flows..
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 Cleverreach data in under 10 minutes.
What data can I load from Cleverreach?
Here are some of the endpoints you can load from Cleverreach:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| groups | /v2/groups | GET | List of all receiver groups/lists | |
| attributes | /v2/attributes | GET | List of global attributes | |
| receivers | /v2/receivers | GET | List of all receivers (emails) | |
| group_receivers | /v2/groups/{group_id}/receivers | GET | Receivers in a specific group (embedded attributes in each receiver) | |
| blacklist | /v2/blacklist | GET | Global blacklist entries | |
| mailings | /v2/mailings | GET | Mailings (supports type filter: draft/finished/waiting) | |
| reports | /v2/reports | GET | Mailing reports | |
| hooks | /hooks/eventhook | GET | List registered webhooks (returns top-level array) | |
| receivers_bounced_v3 | /v3/receivers/bounced | GET | Bounced receivers (v3 - enforces pagination) | |
| Note: Many v2 endpoints return JSON objects or arrays; common pattern: single-resource endpoints return objects with nested arrays (e.g., receivers returned as top-level array or embedded under the response depending on endpoint). Use the REST Explorer (https://rest.cleverreach.com/explorer/v3) for exact per-endpoint response shapes. |
How do I authenticate with the Cleverreach API?
CleverReach uses OAuth2. Include the access token either as ?access_token=... query parameter or as Authorization: Bearer <access_token> header. v3 requires a v3-scoped token.
1. Get your credentials
- Log in to CleverReach account.
- Go to Account > Interfaces > REST API.
- Create a new OAuth app; record the Client ID and Client Secret.
- For Authorization Code flow: set redirect_uri, direct users to authorize, receive code, exchange code at https://rest.cleverreach.com/oauth/token.php to get access_token and refresh_token.
- For Client Credentials flow: POST to https://rest.cleverreach.com/oauth/token.php using client_id:client_secret and grant_type=client_credentials to receive an access_token (scoped to the creating account).
2. Add them to .dlt/secrets.toml
[sources.cleverreach_source] client_id = "your_client_id" client_secret = "your_client_secret" access_token = "your_oauth_access_token"
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 Cleverreach 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 cleverreach_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cleverreach_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cleverreach_data The duckdb destination used duckdb:/cleverreach.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline cleverreach_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 groups and receivers from the Cleverreach 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 cleverreach_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://rest.cleverreach.com", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "groups", "endpoint": {"path": "v2/groups"}}, {"name": "receivers", "endpoint": {"path": "v2/receivers"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cleverreach_pipeline", destination="duckdb", dataset_name="cleverreach_data", ) load_info = pipeline.run(cleverreach_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("cleverreach_pipeline").dataset() sessions_df = data.groups.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cleverreach_data.groups LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cleverreach_pipeline").dataset() data.groups.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 Cleverreach 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
If requests return 401/403, verify you supplied a valid OAuth2 access_token. Use Authorization: Bearer or ?access_token=. Ensure token scope matches the API version (v3 endpoints require v3 tokens) and refresh the token using the refresh_token when expired via POST https://rest.cleverreach.com/oauth/token.php.
Rate limits and errors
API returns standard HTTP error codes with JSON error body: {"error": {"code": , "message": ""}}. Handle 4xx/5xx responses by inspecting the error object. 404 returns the error object shown in docs.
Pagination quirks
Some endpoints (notably v3 /v3/receivers/bounced) enforce pagination. Use the REST Explorer to discover page/limit parameters. For very large receiver lists use the /v3/groups/{id}/get_receivers POST alternative to submit large id_list/email_list parameters (introduced 2025/06).
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 Cleverreach?
Request dlt skills, commands, AGENT.md files, and AI-native context.