Resend Python SDK
Installation
To install Resend Python SDK, simply execute the following command in a terminal:
pip install resend
Setup
First, you need to get an API key, which is available in the Resend Dashboard.
import resend
import os
resend.api_key = "re_yourkey"
Example
You can get an overview about all parameters in the Send Email API reference.
import os
import resend
resend.api_key = "re_yourkey"
params: resend.Emails.SendParams = {
"from": "onboarding@resend.dev",
"to": ["delivered@resend.dev"],
"subject": "hi",
"html": "<strong>hello, world!</strong>",
"reply_to": "to@gmail.com",
"bcc": "bcc@resend.dev",
"cc": ["cc@resend.dev"],
"tags": [
{"name": "tag1", "value": "tagvalue1"},
{"name": "tag2", "value": "tagvalue2"},
],
}
email: resend.Emails.SendResponse = resend.Emails.send(params)
print(email)
Async Support
The SDK supports async operations via httpx. Install the async extra:
pip install resend[async]
Once installed, async methods (suffixed with _async) work automatically — no extra setup needed:
import asyncio
import resend
resend.api_key = "re_yourkey"
async def main():
params: resend.Emails.SendParams = {
"from": "onboarding@resend.dev",
"to": ["delivered@resend.dev"],
"subject": "hi",
"html": "<strong>hello, world!</strong>",
}
email: resend.Emails.SendResponse = await resend.Emails.send_async(params)
print(email)
if __name__ == "__main__":
asyncio.run(main())
Custom async client
To use a custom async HTTP client or configure options like timeouts, set resend.default_async_http_client:
import resend
resend.api_key = "re_yourkey"
resend.default_async_http_client = resend.HTTPXClient(timeout=60)
Legacy configurations that assign an AsyncHTTPClient to
resend.default_http_client are also supported. Async requests select a client
in this order:
- A replacement client assigned to
resend.default_async_http_client. - An
AsyncHTTPClientassigned toresend.default_http_client. - The automatic
HTTPXClient, if httpx is installed.
Setting resend.default_async_http_client = None still permits the legacy
fallback. Prefer the dedicated async setting for new code, so the sync client
remains available for synchronous calls.
Metadata
Release files for resend 2.50.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 | Provenance | Actions |
|---|---|---|---|---|
| resend-2.50.0.tar.gz | 86.2 kB | With provenance | Details for resend-2.50.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| resend-2.50.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for resend-2.50.0-py2.py3-none-any.whl |
Total release size: 212.5 kB
Release files / resend-2.50.0.tar.gz
| Download URL | resend-2.50.0.tar.gz |
|---|---|
| Size | 86.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9224140d22b336397ba34530f3fb166a56977d59e7166dbfc814cf83541ee280
|
|
BLAKE2b-256 checksum How to use checksums |
81ac0077dd598438dff1ee0ffe44cb8dec300f078b4347d7365a6840b950be43
|
| 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 Oct 16, 2026.
Transparency logRelease files / resend-2.50.0-py2.py3-none-any.whl
| Download URL | resend-2.50.0-py2.py3-none-any.whl |
|---|---|
| Size | 126.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4842fdf1a79deaebfe0c6576d0d6390fd732f941f70a43d244d56a1bc156c97b
|
|
BLAKE2b-256 checksum How to use checksums |
022acb87568af993e4e3cdf4977998c46c3accb718166a5b6486186dab96af52
|
| 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 Oct 16, 2026.
Transparency logSecurity for resend 2.50.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for resend-2.50.0.tar.gz
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 Oct 16, 2026.
Transparency logA 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.