EmailOctopus Python API Docs | dltHub
Build a EmailOctopus-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
EmailOctopus is an email marketing service providing a REST API for managing lists, campaigns, contacts, and automations. The REST API base URL is https://emailoctopus.com/api/1.6 and All requests require an API key; v1.x uses the api_key query parameter, v2 uses a Bearer token in the Authorization header..
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 EmailOctopus data in under 10 minutes.
What data can I load from EmailOctopus?
Here are some of the endpoints you can load from EmailOctopus:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| lists | /lists | GET | data | Retrieve all email lists. |
| campaigns | /campaigns | GET | data | List all campaigns. |
| contacts | /contacts | GET | data | Retrieve contacts across lists. |
| automations | /automations | GET | data | List automation workflows. |
| templates | /templates | GET | data | Get email templates. |
How do I authenticate with the EmailOctopus API?
For API version 1.x include api_key=YOUR_KEY as a query parameter. For version 2 include Authorization: Bearer YOUR_TOKEN header. All requests are HTTPS and return JSON.
1. Get your credentials
- Log in to your EmailOctopus account.
- Navigate to Account → API & Integrations (or similar settings page).
- Click Create new API key.
- Give the key a name and copy the generated value.
- Store the key securely; it will be used as
api_key(v1.x) or Bearer token (v2).
2. Add them to .dlt/secrets.toml
[sources.email_octopus_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 EmailOctopus 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 email_octopus_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline email_octopus_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset email_octopus_data The duckdb destination used duckdb:/email_octopus.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline email_octopus_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 lists and campaigns from the EmailOctopus 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 email_octopus_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://emailoctopus.com/api/1.6", "auth": { "type": "api_key", "token": api_key, }, }, "resources": [ {"name": "lists", "endpoint": {"path": "lists", "data_selector": "data"}}, {"name": "campaigns", "endpoint": {"path": "campaigns", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="email_octopus_pipeline", destination="duckdb", dataset_name="email_octopus_data", ) load_info = pipeline.run(email_octopus_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("email_octopus_pipeline").dataset() sessions_df = data.lists.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM email_octopus_data.lists LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("email_octopus_pipeline").dataset() data.lists.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 EmailOctopus 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
API_KEY_INVALID– The supplied API key is missing or incorrect. Verify the key in your dashboard and ensure it is passed correctly (query parameter for v1.x or Bearer header for v2).UNAUTHORISED– Token missing or malformed. Check theAuthorizationheader format.
Rate Limiting
- The API allows up to 10 requests per second. Exceeding this returns HTTP 429 Too Many Requests and may temporarily block the client. Implement back‑off or request throttling.
Pagination
- Collection endpoints return a top‑level
pagingobject withnextandpreviousURLs. Continue fetching whilenextis notnull. Thedataarray contains the records.
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 EmailOctopus?
Request dlt skills, commands, AGENT.md files, and AI-native context.