sendmux-sdk
Optional umbrella package for the Sendmux Python SDK.
Documentation
- Sendmux docs: sendmux.ai/docs
- Management API reference: sendmux.ai/docs/api/introduction
- Mailbox API reference: sendmux.ai/docs/mailbox-api/introduction
- Sending API reference: sendmux.ai/docs/sending-api/introduction
- Source repository: Sendmux/sendmux-sdk
Requirements
- Python 3.10 or newer.
- A send-capable
smx_mbx_*key or owner-approved Sending-resourcesmx_agent_*token for Sending clients. - A mailbox-scoped
smx_mbx_*key or scopedsmx_agent_*token for Mailbox clients. - A root
smx_root_*key for Management clients.
Installation
pip install sendmux-sdk
Connection checks
Check a Management credential without creating resources:
import os
from sendmux_sdk import management
with management.create_management_client(
api_key=os.environ["SENDMUX_MANAGEMENT_API_KEY"]
) as client:
connection = management.ConnectionApi(client).management_get_connection()
print(connection.data.label, connection.data.team.id)
Use data.label for the connection name and data.team.id for its stable team
identifier. Each API surface has its own connection operation:
| Surface | API class | Method |
|---|---|---|
| Management | management.ConnectionApi |
management_get_connection() |
| Mailbox | mailbox.MailboxAPIApi |
mailbox_get_connection() |
| Sending | sending.MetaApi |
sending_get_connection() |
Create each client with the credential for that surface.
Usage
import os
from sendmux_sdk import sending
client = sending.create_sending_client(api_key=os.environ["SENDMUX_SENDING_API_KEY"])
api = sending.EmailsApi(client)
response = api.sending_send_email(
sending.EmailSendRequest(
var_from=sending.Address(email="sender@example.com"),
to=sending.Address(email="recipient@example.com"),
subject="Hello from Sendmux",
html_body="<p>Hello.</p>",
text_body="Hello.",
),
idempotency_key="email_123",
)
print(response.data.message_id)
The umbrella package lazy-loads:
corefromsendmux_coresendingfromsendmux_sendingmailboxfromsendmux_mailboxmanagementfromsendmux_management
Use the per-surface packages directly when an integration only needs one API surface.
Support
Open an issue in Sendmux/sendmux-sdk with the package name, version, and request ID from any API error.
Licence
MIT. See the licence file.
Metadata
Release files for sendmux-sdk 1.1.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 | |
|---|---|---|---|
| sendmux_sdk-1.1.1.tar.gz | 3.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sendmux_sdk-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.1 kB
Release files / sendmux_sdk-1.1.1.tar.gz
| Download URL | sendmux_sdk-1.1.1.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d9e2ffb26d5a18f14f927e3a9d8bcee207315a204d42c2870b3948855d1f24c
|
|
BLAKE2b-256 checksum How to use checksums |
4acf6e16866bc8891fa0d8a8b43fdc4107da00a59fb7a9e73c03a05548bcb5ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 8, 2026.
Transparency logRelease files / sendmux_sdk-1.1.1-py3-none-any.whl
| Download URL | sendmux_sdk-1.1.1-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74442b0a82a63143cb17ad97a62ce0e26708afd9f559649a02b5a2a2e33c30fa
|
|
BLAKE2b-256 checksum How to use checksums |
950e5b8489bc4bc72a4b033f0de5cd30468d8ddf4ee0c7e7e915861a449a1712
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 8, 2026.
Transparency log