Lettermint Python SDK
Official Python SDK for the Lettermint sending and team APIs.
Installation
pip install lettermint
Quick Start
Sending Emails (Synchronous)
from lettermint import Lettermint
email = Lettermint.email("your-sending-token")
response = (
email
.from_("sender@example.com")
.to("recipient@example.com")
.subject("Hello from Python!")
.html("<h1>Welcome!</h1>")
.text("Welcome!")
.send()
)
print(response["message_id"])
Sending Emails (Asynchronous)
from lettermint import AsyncLettermint
email = AsyncLettermint.email("your-sending-token")
response = await (
email
.from_("sender@example.com")
.to("recipient@example.com")
.subject("Hello from Python!")
.html("<h1>Welcome!</h1>")
.send()
)
print(response["message_id"])
The legacy constructor still works for sending-only usage:
client = Lettermint(api_token="your-sending-token")
client.email.from_("sender@example.com").to("recipient@example.com").subject("Hello").send()
Email Options
Multiple Recipients
client.email.from_("sender@example.com").to(
"recipient1@example.com",
"recipient2@example.com"
).subject("Hello").send()
CC and BCC
client.email.from_("sender@example.com").to("recipient@example.com").cc(
"cc1@example.com",
"cc2@example.com"
).bcc("bcc@example.com").subject("Hello").send()
Reply-To
client.email.from_("sender@example.com").to("recipient@example.com").reply_to(
"reply@example.com"
).subject("Hello").send()
RFC 5322 Addresses
client.email.from_("John Doe <john@example.com>").to(
"Jane Doe <jane@example.com>"
).subject("Hello").send()
Attachments
import base64
# Read and encode your file
with open("document.pdf", "rb") as f:
content = base64.b64encode(f.read()).decode()
# Regular attachment
client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Your Document"
).attach("document.pdf", content).send()
# Inline attachment (for embedding in HTML)
client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Welcome"
).html('<img src="cid:logo@example.com">').attach(
"logo.png", logo_content, "logo@example.com"
).send()
Custom Headers
client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Hello"
).headers({"X-Custom-Header": "value"}).send()
Metadata and Tags
client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Hello"
).metadata({"campaign_id": "123", "user_id": "456"}).tag("welcome-campaign").send()
Routing
client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Hello"
).route("my-route").send()
Idempotency Key
Prevent duplicate sends when retrying failed requests:
client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Hello"
).idempotency_key("unique-request-id").send()
Batch Sending
email = Lettermint.email("your-sending-token")
response = email.send_batch([
{
"from": "sender@example.com",
"to": ["recipient@example.com"],
"subject": "Hello from Python!",
"text": "This is a batch email.",
}
])
Both sync and async sending clients support ping():
email.ping()
await AsyncLettermint.email("your-sending-token").ping()
Team API
Use a team API token with Lettermint.api(...). API tokens authenticate with Authorization: Bearer ... and are separate from project sending tokens.
from lettermint import Lettermint
api = Lettermint.api("your-api-token")
domains = api.domains.list({"page[size]": "10"})
team = api.team.retrieve()
message_html = api.messages.html("message-id")
pong = api.ping()
The async Team API client is available through AsyncLettermint.api(...):
from lettermint import AsyncLettermint
api = AsyncLettermint.api("your-api-token")
domains = await api.domains.list({"page[size]": "10"})
message_html = await api.messages.html("message-id")
Endpoint groups are available as domains, messages, projects, routes, stats, suppressions, team, and webhooks.
Webhook Verification
Verify webhook signatures to ensure authenticity:
from lettermint import Webhook
# Create a webhook verifier
webhook = Webhook(secret="your-webhook-secret")
# Verify using headers (recommended)
payload = webhook.verify_headers(request.headers, request.body)
# Or verify using the signature directly
payload = webhook.verify(
payload=request.body,
signature=request.headers["X-Lettermint-Signature"],
)
print(payload["event"])
Static Method
For one-off verification:
from lettermint import Webhook
payload = Webhook.verify_signature(
payload=request.body,
signature=request.headers["X-Lettermint-Signature"],
secret="your-webhook-secret",
)
Custom Tolerance
Adjust the timestamp tolerance (default: 300 seconds):
webhook = Webhook(secret="your-webhook-secret", tolerance=600)
Error Handling
from lettermint import Lettermint
from lettermint.exceptions import (
ValidationError,
ClientError,
HttpRequestError,
TimeoutError,
)
client = Lettermint(api_token="your-sending-token")
try:
response = client.email.from_("sender@example.com").to("recipient@example.com").subject(
"Hello"
).send()
except ValidationError as e:
# 422 errors (e.g., daily limit exceeded)
print(f"Validation error: {e.error_type}")
print(f"Response: {e.response_body}")
except ClientError as e:
# 400 errors
print(f"Client error: {e}")
except TimeoutError as e:
# Request timeout
print(f"Timeout: {e}")
except HttpRequestError as e:
# Other HTTP errors
print(f"HTTP error {e.status_code}: {e}")
Webhook Errors
from lettermint import Webhook
from lettermint.exceptions import (
InvalidSignatureError,
TimestampToleranceError,
JsonDecodeError,
WebhookVerificationError,
)
try:
payload = webhook.verify_headers(headers, body)
except InvalidSignatureError:
print("Invalid signature - request may be forged")
except TimestampToleranceError:
print("Timestamp too old - possible replay attack")
except JsonDecodeError:
print("Invalid JSON in payload")
except WebhookVerificationError as e:
print(f"Verification failed: {e}")
Configuration
Custom Base URL
client = Lettermint(
api_token="your-sending-token",
base_url="https://custom.api.com/v1",
)
Custom Timeout
client = Lettermint(
api_token="your-sending-token",
timeout=60.0, # 60 seconds
)
Context Manager
Both sync and async clients support context managers for proper resource cleanup:
# Sync
with Lettermint(api_token="your-sending-token") as client:
client.email.from_("sender@example.com").to("recipient@example.com").send()
# Async
async with AsyncLettermint(api_token="your-sending-token") as client:
await client.email.from_("sender@example.com").to("recipient@example.com").send()
Type Hints
This SDK is fully typed with py.typed marker. You'll get full autocomplete and type checking in your IDE.
Requirements
- Python 3.9+
- httpx
License
MIT
Release files for lettermint 2.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lettermint-2.4.0.tar.gz | 32.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lettermint-2.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.4 kB
Release files / lettermint-2.4.0.tar.gz
| Download URL | lettermint-2.4.0.tar.gz |
|---|---|
| Size | 32.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70251532d9d024a84620154e0e3135bf37bfb2d354938b54c2d272ad3d0c1583
|
|
BLAKE2b-256 checksum How to use checksums |
8123cb83313bf83b259030f41934798c897b4d2f6e04a927ede9d0df8b7407fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / lettermint-2.4.0-py3-none-any.whl
| Download URL | lettermint-2.4.0-py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
240f70802eb39e3c1394777c80d8290138040f8ca8f2b42f8c51d67064e86ec0
|
|
BLAKE2b-256 checksum How to use checksums |
31527434cb07033ce9f0ce68d71a3893106d3a1825525031b5a1854391535552
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency log