WazobiaMail developers and programmers

For developers and programmers

Send email from your app in one HTTP request.

Transactional email stops being a side project. Send login codes, receipts and alerts from the same codebase that handles the rest of the request, and pay for the messages you actually send.

Your addressnotifications@yourapp.com

01What changes for you

The problem you have,
and what fixes it.

A delayed login code or missing receipt becomes your support problem. Other providers start at $20/month before you send one message.

01 /

Ship transactional email in an afternoon

One endpoint, one API key, one POST. There is no SDK to learn and no message queue to run, so you can send a password reset on the day you decide to, not the quarter after.

02 /

Pay for what you send

Sending is priced per 1,000 recipients, and purchased credits stay in your account until you use them. A project in testing does not carry a monthly invoice for messages it never sent.

03 /

Keep credentials where they belong

Your key lives in your server environment or secret store, never in browser code or a public repository. Create a separate key per service and revoke it from the dashboard if it leaks.

04 /

See what actually happened

Accepted is not delivered. Delivery activity records the result of each message so you can answer "did my customer get the receipt?" with evidence instead of a guess.

02How it works

Live in three steps.

Send from your app through HTTP or SMTP. Pay per 1,000 recipients from ₦250 / $0.50. Manage keys, domains and delivery activity in one place.

01 /

Create an account and verify your domain

Verify the domain you send from so receiving services can identify your messages. Your dashboard shows the records to publish and the verification status.

02 /

Create a sending key

Generate an API key in your workspace and store it in your server environment as WAZOBIA_API_KEY. Keep it out of client-side code and out of your repository.

03 /

Send your first message

POST to the sending endpoint with your key and the message details. The response tells you whether the message was accepted for sending, and the activity log follows it from there.

03What you get

Everything for
notifications@yourapp.com

Send from your app through HTTP or SMTP. Pay per 1,000 recipients from ₦250 / $0.50. Manage keys, domains and delivery activity in one place.

Connect your application ↗

Common needs, already handled.

  • Send welcome emails and password-reset links from your application.
  • Trigger receipts, booking confirmations and account alerts.
  • Check sending activity when a customer reports a missing message.

Sending keys, DNS records, mailbox credentials and delivery activity all live in one workspace, so you are not hunting across dashboards when something needs attention.

Try it in your own code

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 ↗ Test in Postman ↗

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 '{
  "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>"
  }
}'

04Good questions

Plain answers.

All your questions, answered ↗
How do I send email from my application?

Use the HTTP sending endpoint with your API key in the request header, or connect an application that already speaks authenticated SMTP. Both routes reach the same sending infrastructure, so you can migrate between them without rewriting your message logic.

What is the difference between SMTP and the email API?

SMTP suits tools that already accept a mail host, port and credentials. The HTTP API suits codebases that already make HTTP requests from a backend. The guide on choosing between them walks through the decision in more detail.

How are sending rates and limits enforced?

Each plan sets hourly, daily and monthly allowances plus a per-minute rate limit. The active plan and your account status determine which limits apply, and the delivery activity view shows the outcome of every send.

Does the API protect against sending duplicates?

Treat every send as an operation you can retry and record the message reference returned with each accepted message. That reference is what lets you reconcile activity, investigate a failed send and answer a support question with a real result.

Where should I keep my API key?

Keep it in your server environment or a secret store. Do not put it in browser code, a public repository or a screenshot. Create a separate key for each integration when practical, and revoke a key from your dashboard if it is ever exposed.

For developers and programmers

Send email from your app in one HTTP request.

Create your account

Free sending tier available. Paid plans add hosted mailboxes and larger sending allowances.

Already have an account? Sign in ↗