.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
Move your app's notification emails to a provider that signs a BAA
Password resets, appointment notices and result alerts often carry PHI, and many email providers won't sign a BAA. Paubox Email API will, on every plan, and you can switch over with a REST API, SMTP or one of ten SDKs. Start for free
Do this with AI
Paste the following prompt into your AI assistant:
Our app sends notification emails through a general-purpose email provider that won't sign a BAA. Explain what switching to the Paubox Email API would involve, whether we could keep our existing code mostly as is, and why it's worth moving.
Paubox Email API
Switching is smaller than it sounds
Your notification email works today, so moving it feels like a project. Paubox offers a REST API, an SMTP option and SDKs in ten languages, plus migration guides for the most common email providers. Point your existing sending code at Paubox, verify your sending domain, and your notifications go out encrypted with a business associate agreement (BAA) in place.
Migration guides
Step-by-step guides for moving from the email providers healthcare apps use most
SMTP or REST
Use SMTP to keep your current sending code, or move to the REST API and SDKs
A BAA on every plan
Including the free tier, with 300 emails a month. Paubox is HITRUST certified.
Perfect for: Startups that launched on a general-purpose email provider, product teams adding health features to an existing app, and engineers who just learned their notifications contain PHI.
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.