A Python client is one part of the integration. Your application still owns the event database, secret storage, callback and delivery reconciliation.
Install the reviewed client
Use the versioned Python SDK artifact or the documented HTTPS contract from your server environment. Pin dependencies and keep the API base URL on the canonical Emailer API domain.
Load the sending key from an environment-backed secret store. Never place it in a notebook, browser bundle, fixture committed to source or exception message.
Verify a real event
Expose an HTTPS callback on the exact verified sending domain and verify the HMAC proof over the raw body before querying your database. Return only the documented signed response for a matching fresh event.
For payment receipts and paid orders, follow the direct Stripe verification path described in the product documentation.
Validate, send and reconcile
Call validation on the intended payload, then send with a stable event identifier and idempotency key. Store the returned message ID and inspect later delivery events.
A Python exception after submission does not show whether the message was accepted. Reconcile the original key and message history before retrying.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.