Mailtrap Python API Docs | dltHub
Build a Mailtrap-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Mailtrap is an email testing service providing APIs for sending, testing, and managing emails. The REST API base URL is https://mailtrap.io/api and All requests require an API token passed as Authorization: Bearer <token> or Api-Token: <token> 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 Mailtrap data in under 10 minutes.
What data can I load from Mailtrap?
Here are some of the endpoints you can load from Mailtrap:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| inboxes | /api/accounts/{account_id}/inboxes | GET | List all inboxes in the account | |
| inbox | /api/accounts/{account_id}/inboxes/{inbox_id} | GET | Retrieve details of a specific inbox | |
| messages | /api/accounts/{account_id}/inboxes/{inbox_id}/messages | GET | List messages in an inbox (up to 30 per page) | |
| message | /api/accounts/{account_id}/inboxes/{inbox_id}/messages/{message_id} | GET | Retrieve a single message | |
| account | /api/accounts/{account_id} | GET | Get basic account information (inferred) |
How do I authenticate with the Mailtrap API?
Authentication uses an API token. Include it in the request header either as Authorization: Bearer YOUR_API_TOKEN or as Api-Token: YOUR_API_TOKEN.
1. Get your credentials
- Log in to your Mailtrap account.
- Navigate to Settings → API Tokens.
- Click Generate new token.
- Give the token a name and select the required permissions.
- Copy the generated token and store it securely; it will be used for all API calls.
2. Add them to .dlt/secrets.toml
[sources.mailtrap_source] api_token = "your_api_token_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 Mailtrap 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 mailtrap_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mailtrap_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mailtrap_data The duckdb destination used duckdb:/mailtrap.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline mailtrap_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 inboxes and messages from the Mailtrap 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 mailtrap_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://mailtrap.io/api", "auth": { "type": "bearer", "token": api_token, }, }, "resources": [ {"name": "inboxes", "endpoint": {"path": "api/accounts/{account_id}/inboxes"}}, {"name": "messages", "endpoint": {"path": "api/accounts/{account_id}/inboxes/{inbox_id}/messages"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mailtrap_pipeline", destination="duckdb", dataset_name="mailtrap_data", ) load_info = pipeline.run(mailtrap_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("mailtrap_pipeline").dataset() sessions_df = data.messages.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mailtrap_data.messages LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mailtrap_pipeline").dataset() data.messages.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 Mailtrap 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 the API token is missing, malformed, or lacks the required scopes, the API returns a 401 Unauthorized response. Ensure the Authorization: Bearer <token> or Api-Token: <token> header is present and that the token was generated with appropriate permissions.
Rate limiting
Mailtrap enforces a general limit of 150 requests per 10 seconds per token (with lower limits for some sub‑APIs). Exceeding the limit returns a 429 Too Many Requests error. Respect the X‑RATELIMIT‑LIMIT and X‑RATELIMIT‑REMAINING response headers and implement exponential back‑off before retrying.
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 Mailtrap?
Request dlt skills, commands, AGENT.md files, and AI-native context.