WazobiaMail integrations

Works with your stack

A natural fit for your stack.

Connect your application with WazobiaMail through HTTP API or authenticated SMTP, and connect Google through OAuth.

For developers · Backend written in Rust

Ship your app.
Let us handle the email.

A signup needs its login code. An order needs its receipt. Send both from your backend with one HTTP request.

Your stack is welcome here.

  1. Create an account and verify your sending domain.
  2. Create an API key and save it in your server environment as WAZOBIA_API_KEY.
  3. Replace the sender and recipient below, then run the example on your server.

Use HTTP for new integrations or authenticated SMTP for tools you already use. Keep keys out of browser code and public repositories.

Follow the quickstart ↗

A successful response means accepted for sending. Check delivery activity to see what happens next.

curl -X POST https://app.wazobiamail.com/api/v1/sending/messages   -H 'Content-Type: application/json'   -H "X-API-Key: $WAZOBIA_API_KEY"   -d '{
  "envelopeSender": "hello@yourbrand.com",
  "to": [
    "you@example.com"
  ],
  "content": {
    "from": "Your Brand <hello@yourbrand.com>",
    "subject": "Welcome to Your Brand",
    "htmlBody": "<p>Your account is ready. Welcome aboard!</p>"
  }
}'

Try it now.

Send an email straight to your inbox.

Separate addresses with commas. Maximum 3.
Up to 1,000 characters.

Test your own domain and message

Use your verified domain and sending API key. This test uses your account's sending allowance.

Your key is used only for this request and cleared after submission. Revoke your temporary test key when you finish.

01 / HTTP

From your backend.

Send through the email API from any server that can make HTTP requests. Create a sending key in your account and keep it in your server environment.

Explore the email API ↗
02 / SMTP

With your existing tools.

Connect applications that support authenticated SMTP. Use the host, port and credentials shown for your configured sending service.

SMTP or HTTP? ↗
03 / GOOGLE

Through your account.

Connect Google through OAuth. Review and grant the permissions for Gmail sending and Contacts access according to your workflow.

Explore Google connections ↗

Your name belongs in your email

Your brand.
Every time you press send.

Create your account

Custom domain inboxes for you and your team. Email sending for your apps.