Skip to main content

Official Python SDK for the Anypost email API.

Project description

Anypost Python SDK

The official Python client for the Anypost email API.

Requires Python 3.9+. Built on httpx, with sync and async clients.

Install

pip install anypost

Quickstart

from anypost import Anypost

client = Anypost("ap_your_api_key")

result = client.email.send({
    "from": "Acme <you@yourdomain.com>",
    "to": ["someone@example.com"],
    "subject": "Hello from Anypost",
    "html": "<p>It worked.</p>",
})
print(result["id"])

The constructor also reads ANYPOST_API_KEY from the environment:

client = Anypost()

Keep the key server-side. It is a bearer credential; never ship it to a browser or mobile app.

Request bodies are plain dicts that match the API one-to-one — including the "from" key, which a dict literal accepts even though from is a reserved word. Responses are dicts too, typed with TypedDict for editor autocomplete.

Async

Every operation has an async twin on AsyncAnypost. Same methods, same shapes — await them, and iterate pages with async for.

import asyncio
from anypost import AsyncAnypost

async def main():
    async with AsyncAnypost("ap_your_api_key") as client:
        result = await client.email.send({
            "from": "Acme <you@yourdomain.com>",
            "to": ["someone@example.com"],
            "subject": "Hello",
            "html": "<p>It worked.</p>",
        })
        print(result["id"])

asyncio.run(main())

The rest of this README shows the sync client. The async client is identical with await.

Sending

One of text, html, or template_id is required. All recipients in to, cc, and bcc share one envelope and count against a combined limit of 50.

client.email.send({
    "from": "Acme <you@yourdomain.com>",
    "to": ["a@example.com", "b@example.com"],
    "cc": ["team@example.com"],
    "reply_to": "support@yourdomain.com",
    "subject": "Receipt #4823",
    "html": "<p>Thanks for your order.</p>",
    "text": "Thanks for your order.",
    "tags": ["receipt"],
})

Pass attachment content as raw bytes and the client base64-encodes it; pass an already-encoded str and it is sent as-is. The request body is capped at 5 MB.

from pathlib import Path

client.email.send({
    "from": "you@yourdomain.com",
    "to": ["someone@example.com"],
    "subject": "Your report",
    "text": "Attached.",
    "attachments": [
        {"filename": "report.pdf", "content": Path("report.pdf").read_bytes()},
    ],
})

Send with a published template and per-recipient variables:

client.email.send({
    "from": "you@yourdomain.com",
    "to": ["someone@example.com"],
    "template_id": "template_018f2c5e-3a40-7a91-9c25-3a0b1d5e6f78",
    "variables": {"name": "Ada", "plan": "pro"},
})

Batch

Send 1 to 100 independent messages in one request. defaults fills any field an entry omits.

result = client.email.send_batch({
    "defaults": {"from": "you@yourdomain.com"},
    "emails": [
        {"to": ["a@example.com"], "subject": "Hi A", "text": "..."},
        {"to": ["b@example.com"], "subject": "Hi B", "text": "..."},
    ],
})

A batch with mixed outcomes returns HTTP 207 and resolves normally. Inspect each entry rather than relying on a raised error:

print(result["summary"])  # {"total": ..., "queued": ..., "failed": ...}

for entry in result["data"]:
    if entry["status"] == "queued":
        print(entry["index"], entry["id"])
    else:
        print(entry["index"], entry["error"]["type"], entry["error"]["message"])

Domains

Manage sending domains under client.domains. Add a domain, publish the CNAMEs it returns, then verify.

domain = client.domains.create({"name": "example.com"})

for record in domain["dns_records"]:
    print(record["type"], record["name"], "->", record["value"])

verify always returns the current domain — a still-pending domain does not raise. Read status and verification_failure, and poll while DNS propagates.

checked = client.domains.verify(domain["id"])
if checked["status"] != "verified":
    print(checked["verification_failure"])

get, update (tracking config only), and delete round out the resource:

client.domains.update(domain["id"], {
    "tracking": {"opens_enabled": True, "clicks_enabled": True, "subdomain": "track"},
})
client.domains.delete(domain["id"])

API keys

Manage keys under client.api_keys. The plaintext secret comes back only once, on create, as key:

created = client.api_keys.create({
    "name": "Production server",
    "permissions": "send_only",
    "allowed_domains": ["example.com"],
})
print(created["key"])  # store now; never retrievable again

client.api_keys.update(created["id"], {"name": "Production server", "permissions": "full"})
client.api_keys.delete(created["id"])

get returns metadata only — key_prefix, never the secret. Permission and restriction changes take up to 5 minutes to propagate through the gateway cache.

Templates

Templates use a draft/published model: edits land in a draft, and publish promotes it. A template can't be used for sending until it's published.

template = client.templates.create({
    "name": "Welcome email",
    "kind": "html",
    "html": "<h1>Welcome, {{ name }}</h1>",
})

client.templates.update_draft(template["id"], {
    "subject": "Welcome to Acme",
    "html": "<h1>Welcome, {{ name }}</h1>",
})
client.templates.publish(template["id"])

kind is html or markdown and is immutable once set. The plain-text body is always derived server-side. get_draft, delete_draft, duplicate, get, update (name only), and delete round out the resource. Send with a published template via template_id (see Sending).

Suppressions

A suppression blocks sends to an address, scoped to a topic. The wildcard * blocks every topic; a specific topic (e.g. marketing) leaves transactional traffic untouched. Bounces and complaints write * automatically.

client.suppressions.create({
    "email": "alice@example.com",
    "topic": "marketing",
    "note": "Customer requested removal",
})

row = client.suppressions.get("alice@example.com", "*")
client.suppressions.delete("alice@example.com", "marketing")

list accepts email_contains, topic, reason, and origin filters. list_for_email returns every row for an address across all topics; delete_for_email removes them all.

for s in client.suppressions.list({"reason": "complaint"}):
    print(s["email"], s["topic"], s["suppressed_at"])

Webhooks

Manage webhook subscriptions under client.webhooks. The signing_secret comes back only once, on create; later reads return only signing_secret_prefix.

webhook = client.webhooks.create({
    "name": "Production events",
    "url": "https://hooks.example.com/anypost",
    "events": ["email.delivered", "email.bounced", "email.complained"],
})
print(webhook["signing_secret"])  # store now; never retrievable again

update sets the name, URL, events, and status together — set status to "disabled" to pause delivery, "active" to resume. test sends one synthetic webhook.test event and returns the outcome even when the endpoint fails. rotate_secret issues a new secret and keeps the previous one valid for a 24-hour grace window; get, list, and delete round out the resource.

result = client.webhooks.test(webhook["id"])
if not result["delivered"]:
    print(result["status_code"], result["error"])

rotated = client.webhooks.rotate_secret(webhook["id"])

Verifying deliveries

verify_webhook_signature is a standalone function — it needs the signing secret, not an API key, so call it in your handler without a client. Pass the raw request body (the exact bytes, before JSON parsing), the Anypost-Signature header, and the secret. It returns on success and raises WebhookVerificationError otherwise. unwrap_webhook_event does the same and returns the parsed delivery.

from anypost import unwrap_webhook_event, WebhookVerificationError

try:
    delivery = unwrap_webhook_event(raw_body, signature_header, secret)
    for event in delivery["events"]:
        print(event["type"], event["data"]["email_id"])
except WebhookVerificationError as err:
    # err.reason: "no_match" | "timestamp_out_of_tolerance" | ...
    return Response(status_code=400)

Reach for verify_webhook_signature when something else has already parsed the body. Keep the raw bytes for the verify step, then use your framework's parsed object once it passes:

from anypost import verify_webhook_signature, WebhookVerificationError

@app.post("/anypost")
async def anypost_webhook(request):
    raw = await request.body()
    try:
        verify_webhook_signature(raw, request.headers["anypost-signature"], secret)
    except WebhookVerificationError:
        return Response(status_code=400)
    for event in (await request.json())["events"]:
        handle(event)
    return Response(status_code=204)

Deliveries older than five minutes are rejected by default to bound replay; pass tolerance_seconds to widen, narrow, or disable (0) that check. During a secret rotation the header carries a v1= component per active secret, and a match on any one passes — so deliveries keep verifying while you redeploy.

Events

client.events.list pages the team's event stream, newest-first. The window defaults to the last 24 hours and is clamped to your plan's retention. Events are read-only and not addressable by id — there is no get.

for event in client.events.list({"event_type": "email.bounced"}):
    print(event["occurred_at"], event["recipient"], event["bounce_classification"])

Filter by start, end, event_type, recipient, email_id, message_id, domain, topic, campaign, template_id, and tags. All filters are exact-match, except tags, which takes a list and matches an event carrying any of the given tags. A filter value that matches no row returns an empty page. This is also how you backfill the gap after a webhook endpoint was disabled — page the events that occurred during the outage once it's healthy.

# Events tagged "onboarding" OR "welcome", that also bounced.
page = client.events.list({
    "tags": ["onboarding", "welcome"],
    "event_type": "email.bounced",
})

Pagination

List endpoints return a Page. Read one page directly, or iterate it to walk every page — the client fetches each one as needed.

page = client.domains.list({"limit": 50})
page.data         # this page's items
page.has_more     # whether another page exists
page.next_cursor  # pass as "after" to fetch it yourself

for domain in client.domains.list():
    print(domain["name"])  # every domain, across all pages

On the async client, await the call and iterate with async for:

async for domain in await client.domains.list():
    print(domain["name"])

Errors

A failed request raises an AnypostError subclass. Branch on err.type, the stable machine-readable code, not on the HTTP status.

from anypost import AnypostError, ValidationError, RateLimitError

try:
    client.email.send({"from": from_, "to": to, "subject": subject, "html": html})
except ValidationError as err:
    print(err.errors)  # {"from": ["The from field is required."]}
except RateLimitError as err:
    print(err.retry_after)  # seconds, or None
except AnypostError as err:
    print(err.type, err.status, err.message)
Class type Status
ValidationError validation_error 400, 422
AuthenticationError authentication_error 401
PermissionError permission_error 403
NotFoundError not_found 404
ConflictError idempotency_concurrent, webhook_rotation_in_progress 409
IdempotencyMismatchError idempotency_mismatch 422
RateLimitError rate_limit_exceeded 429
PayloadTooLargeError payload_too_large 413
APIError internal_error, provisioning_error 5xx
APIConnectionError connection_error none

Every error carries type, status, message, request_id, and the parsed raw body.

Retries and idempotency

The client retries 429, 502, 503, and network failures up to max_retries times (default 2), with exponential backoff and full jitter. It honors Retry-After.

Sends are made safe to retry automatically: when retries are enabled and you do not pass an idempotency_key, the client generates one and reuses it across attempts, so a retried send cannot deliver twice. Pass your own key to dedupe across process restarts:

client.email.send(message, idempotency_key=order_id)

Configuration

Anypost(api_key="ap_your_api_key", base_url=..., timeout=..., max_retries=...)
Option Default Description
api_key ANYPOST_API_KEY Bearer credential (ap_...).
base_url https://api.anypost.com/v1 API base URL.
timeout 30.0 Per-request timeout, in seconds.
max_retries 2 Automatic retries for transient failures.
default_headers {} Extra headers sent on every request.
http_client a new one Bring your own httpx.Client / httpx.AsyncClient.

AsyncAnypost takes the same arguments. send and send_batch accept a per-call idempotency_key.

Close the client when you're done, or use it as a context manager:

with Anypost() as client:
    client.email.send(message)

# async
async with AsyncAnypost() as client:
    await client.email.send(message)

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

anypost-1.0.0.tar.gz (26.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

anypost-1.0.0-py3-none-any.whl (41.5 kB view details)

Uploaded Python 3

File details

Details for the file anypost-1.0.0.tar.gz.

File metadata

  • Download URL: anypost-1.0.0.tar.gz
  • Upload date:
  • Size: 26.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for anypost-1.0.0.tar.gz
Algorithm Hash digest
SHA256 66893fcaf703f2a31d5253e6fa54e745b1d73d311a0dc37a72d41d56fe840c69
MD5 67fb47d65bf7b23c7a826a73b5e5f32d
BLAKE2b-256 a727a2149e445fed41b4237b37b3f6d21ce20e71a8a9e8507401ce97a8264313

See more details on using hashes here.

Provenance

The following attestation bundles were made for anypost-1.0.0.tar.gz:

Publisher: release.yml on anypost/anypost-python

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file anypost-1.0.0-py3-none-any.whl.

File metadata

  • Download URL: anypost-1.0.0-py3-none-any.whl
  • Upload date:
  • Size: 41.5 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for anypost-1.0.0-py3-none-any.whl
Algorithm Hash digest
SHA256 429343167da5c3f237ee9a8143c8ce03a142cf88da43716fd4e0a454e5cd92f9
MD5 339cb12ad0e53dc4567598ae2cd613aa
BLAKE2b-256 16f46abf2bcf023ac43d6221092e75615aab3bf86e440da16ed0c812b8f7876c

See more details on using hashes here.

Provenance

The following attestation bundles were made for anypost-1.0.0-py3-none-any.whl:

Publisher: release.yml on anypost/anypost-python

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page