AMG Mail SDK
Server-side client for the transactional-only AMG Mail API. Keep keys and callback secrets in your server secret manager.
Production sends require a fixed approved template and a verified event bound to the exact recipient and rendered content. Raw messages and arbitrary transaction labels are rejected. Start at https://amgmail.amgcc.space/setup and follow https://amgmail.amgcc.space/docs#event-proof.
New transactional resources: transactional.status, transactional.templates.create, transactional.integrations.create / remove, and transactional.events.create. Verify a source event, attach its returned ID/type as metadata.transaction_id / metadata.event, call emails.validate, then emails.send with a stable idempotency key. The callback authenticates application assertions; it is application attestation. Payment receipts and paid-order confirmations instead require an independent Stripe connection.
No automatic retries or redirects. HTTP acceptance means queued, not delivered. Marketing, bulk recipients, arbitrary content, attachments and custom headers are unavailable in production. SDK methods for existing contact/template/legacy resources do not override server policy.
Install from the public package registry:
python -m pip install amgmail
See the OpenAPI contract at https://amgmail.amgcc.space/openapi.json for exact payloads and response fields. Versioned website downloads remain available in the guide.
Independent payment verification is available through transactional.providers.create / remove and transactional.events.create with provider_connection_id. Stripe test-mode payments do not authorize production mail. Copy the complete Node/Python example at https://amgmail.amgcc.space/docs#stripe.
Use emails.metrics for delivery, bounce, complaint and engagement counts/rates; analytics.settings.get and analytics.settings.update control tracking. Open/click observations may come from privacy proxies or scanners. Sensitive messages and links are excluded. Dashboard: https://amgmail.amgcc.space/analytics.
Metadata
Release files for amgmail 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| amgmail-0.3.1.tar.gz | 15.4 kB | Without provenance | Details for amgmail-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| amgmail-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for amgmail-0.3.1-py3-none-any.whl |
Total release size: 24.1 kB
Release files / amgmail-0.3.1.tar.gz
| Download URL | amgmail-0.3.1.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d2f17d37c77950dcf30cb873178a8fc77f1dbf89e2d6800b956d0043f4922ad
|
|
BLAKE2b-256 checksum How to use checksums |
9753097791930d00e2cb9039955313ef964519cbd5b7cfbd3b590951ef98c476
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.14
|
Release files / amgmail-0.3.1-py3-none-any.whl
| Download URL | amgmail-0.3.1-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b86ff1ac739651e42c0aa9ae806d69a044400dfe3b5f1105d6fc31a81d856fd3
|
|
BLAKE2b-256 checksum How to use checksums |
99129fbcbc78f4bf0c43519e371989119c8f2e1e4b1d9293bb784cf5ce5976c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.14
|
Security for amgmail 0.3.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.