Campaign Monitor Python API Docs | dltHub

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

Last updated:

Campaign Monitor is an email marketing platform providing a REST API for managing campaigns, subscribers, lists, and performance analytics. The REST API base URL is https://api.createsend.com/api/v3.3/ and Supports both HTTP Basic Auth with an API key and OAuth 2.0 tokens..

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


What data can I load from Campaign Monitor?

Here are some of the endpoints you can load from Campaign Monitor:

ResourceEndpointMethodData selectorDescription
client_campaignsclients/{clientid}/campaigns.jsonGETRetrieves a list of sent campaigns for a client. Supports pagination, date filtering, and tag filtering.
client_suppression_listclients/{clientid}/suppressionlist.jsonGETRetrieves the suppression list for a client. Supports pagination and ordering.
campaign_recipientscampaigns/{campaignid}/recipients.jsonGETRetrieves a paginated list of recipients for a campaign.
campaign_bouncescampaigns/{campaignid}/bounces.jsonGETRetrieves a paginated list of bounces for a campaign. Supports date filtering.
segment_active_subscriberssegments/{segmentid}/active.jsonGETRetrieves all active subscribers that match rules for a segment. Supports date filtering and pagination.

How do I authenticate with the Campaign Monitor API?

Authentication is performed via either HTTP Basic Authentication using an API key as the username (with a blank or dummy password) or using OAuth 2.0 access tokens passed in the Authorization header.

1. Get your credentials

  1. Log in to your Campaign Monitor account. 2. Click your profile image in the top-right corner of the dashboard. 3. Select 'Account settings' from the menu. 4. Navigate to the 'API keys' section. 5. If you do not already have a key, click 'Generate API key' to create one. Click 'Show API key' to reveal it if necessary. Note that you must have a verified email address associated with your account to access these settings.

2. Add them to .dlt/secrets.toml

[sources.campaign_monitor_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 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 Campaign Monitor 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 campaign_monitor_pipeline.py

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

Pipeline campaign_monitor_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset campaign_monitor_data The duckdb destination used duckdb:/campaign_monitor.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 clients and campaigns from the Campaign Monitor 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 campaign_monitor_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.createsend.com/api/v3.3/", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "client_campaigns", "endpoint": {"path": "clients/{clientid}/campaigns.json"}}, {"name": "segment_active_subscribers", "endpoint": {"path": "segments/{segmentid}/active.json"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="campaign_monitor_pipeline", destination="duckdb", dataset_name="campaign_monitor_data", ) load_info = pipeline.run(campaign_monitor_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("campaign_monitor_pipeline").dataset() sessions_df = data.client_campaigns.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM campaign_monitor_data.client_campaigns LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("campaign_monitor_pipeline").dataset() data.client_campaigns.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 Campaign Monitor 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 Campaign Monitor?

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

Available Pipelines