.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Paubox Email API
Email lab results straight to a patient
Send results, reminders and notifications from your own application with a REST API. Every message is encrypted in transit and covered by a BAA, and the patient reads it in their regular inbox. Start for free
Do this with AI
Paste the following prompt into your AI assistant:
We want to email lab results to patients directly from our application. Explain how the Paubox Email API keeps those messages HIPAA compliant, what happens if a patient's email server can't accept encryption, and why we'd use it over a general-purpose email provider.
Email API
From your application to the patient's inbox
Your application already knows when a result is ready. The Paubox Email API sends the notification, with the report attached, encrypted with TLS 1.2 or higher. If a patient's mail server can't accept an encrypted connection, the message goes to the Secure Message Center rather than out unencrypted. You can check delivery and open status for every message.
Never sent unencrypted
If a recipient's server can't accept TLS, the message is delivered through a secure portal instead
Know it arrived
Check delivery and open status for each message, or receive webhook events as they happen
A BAA on every plan
Including the free tier, with 300 emails a month and SDKs in ten languages
Perfect for: Health tech teams sending results or appointment reminders, labs and specialty providers notifying patients directly, and anyone moving off an email provider that won't sign a BAA.
Get started
You can do this and more with Paubox
Encrypted email, inbound security, forms and an email API, with a business associate agreement (BAA) on every plan.