One send API
Stable JSON payload across every provider, plus SendGrid and Resend compatibility endpoints.
Send through the providers you already trust. Connect Resend, SendGrid, Postmark, Mailgun, Amazon SES and more, then use one API, SMTP or MCP endpoint — with automatic failover, delivery analytics and your own keys.
curl https://api.opensender.email/v1/send \
-H "Authorization: Bearer os_live_…" \
-H "Idempotency-Key: order-1842" \
-H "Content-Type: application/json" \
-d '{
"from": "Acme <hello@acme.com>",
"to": ["user@example.com"],
"subject": "Your receipt",
"html": "<p>Thanks for your order.</p>"
}'
Works with the providers you already pay for
Keep provider choice, credentials and routing in one control plane. Change providers without shipping code, and see exactly what happened to every message.
Stable JSON payload across every provider, plus SendGrid and Resend compatibility endpoints.
Serialize attempts across your provider chain. If one API fails, the next one takes over.
Delivery, bounce, complaint and failure rates by provider, with reputation alerts.
SPF, DKIM and DMARC checks before a domain can send. Domain-level allow lists per API key.
Hard bounces and complaints are added automatically, then checked before every send.
Idempotency keys, per-key rate limits, cursor-paginated logs and signed provider webhooks.
No migration project. Add your existing provider credentials, verify one domain, then change the base URL.
Paste an API key for Resend, SendGrid, Postmark, Mailgun, SES or SMTP. Credentials are encrypted at rest.
Publish SPF, DKIM and DMARC records, then run the built-in DNS check.
Create an os_live_ key and point your app at api.opensender.email.
Provider usage is billed by your provider. OpenSender adds routing, logs and controls on top.
For prototypes and small projects.
For products in production.
For high-volume senders.
Free to start. Bring your own provider. Keep your deliverability.