Postmark Python API Docs | dltHub

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

Last updated:

Postmark is an email delivery service that provides a REST API for sending transactional emails, managing domains, and accessing server-level data. The REST API base URL is https://api.postmarkapp.com and all requests require an API token sent via specific X-Postmark-*-Token headers.

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


What data can I load from Postmark?

Here are some of the endpoints you can load from Postmark:

ResourceEndpointMethodData selectorDescription
outbound_messages/messages/outboundGETMessagesRetrieve list of outbound messages
inbound_messages/messages/inboundGETInboundMessagesRetrieve list of inbound messages
templates/templatesGETTemplatesList all email templates
message_streams/message-streamsGETMessageStreamsList all message streams in a server
webhooks/webhooksGETWebhooksList all configured webhook endpoints

How do I authenticate with the Postmark API?

Postmark API authentication requires providing an API token via specific HTTP headers, either 'X-Postmark-Server-Token' for server-level privileges or 'X-Postmark-Account-Token' for account-level privileges. Both the header name and value are case-insensitive.

1. Get your credentials

To obtain your API credentials, log in to your Postmark account. For server-level actions (e.g., sending emails, searching messages), navigate to your specific Server, then click the 'API Tokens' tab to copy your Server API token. For account-level actions (e.g., managing servers or domains), navigate to your account settings and locate the Account API token in the 'API Tokens' tab. Always treat these tokens as sensitive credentials.

2. Add them to .dlt/secrets.toml

[sources.postmark_source] server_token = "your_server_api_token_here" account_token = "your_account_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 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 Postmark 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 postmark_pipeline.py

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

Pipeline postmark_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset postmark_data The duckdb destination used duckdb:/postmark.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 servers and email from the Postmark 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 postmark_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.postmarkapp.com", "auth": {"type": "api_key", "api_key": api_token, "name": "X-Postmark-Server-Token or X-Postmark-Account-Token", "location": "header"}, }, "resources": [ {"name": "outbound_messages", "endpoint": {"path": "messages/outbound", "data_selector": "Messages"}}, {"name": "inbound_messages", "endpoint": {"path": "messages/inbound", "data_selector": "InboundMessages"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="postmark_pipeline", destination="duckdb", dataset_name="postmark_data", ) load_info = pipeline.run(postmark_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("postmark_pipeline").dataset() sessions_df = data.outbound_messages.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM postmark_data.outbound_messages LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("postmark_pipeline").dataset() data.outbound_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 Postmark 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 Postmark?

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

Available Pipelines