For the first thing you ship.
- 5,000 emails a month, 200 a day
- 1 sending domain, 1 contact book, 1 team member, 1 webhook
- Full API, SMTP relay, webhooks, suppression
- One-time codes; SMS prepaid from the wallet
Notix is a transactional and marketing email platform: a JSON send API, an SMTP relay, OTP codes by email and SMS, and one suppression list across all of it. From Kenya you pay for it in shillings, from a prepaid wallet topped up by card, bank transfer or mobile money, so you never need a dollar card. The free plan covers 5,000 emails a month; the price per email below is the one the app bills with.
Your team holds a wallet in shillings. You top it up through HitchPay by card, bank transfer or mobile money, and Pro months and any usage past the free allowance are deducted from it. The prices shown here are read live from the same price list the app bills with, for a visitor in Kenya; elsewhere they show in dollars.
For the first thing you ship.
Prices shown in USD. Pay by card.
For committed volume and procurement.
Every wallet movement has a receipt on your billing page, and the ledger lists each charge with the balance after it. Wallet payments are not refundable; unused balance stays until you use it.
A JSON endpoint with typed SDKs for TypeScript, Python, Go and PHP, and an SMTP relay for anything that already speaks SMTP. A receipt sent from a Rails app and one sent from a Node service go through the same pipeline and are tracked the same way.
One verification API sends a code by email or, for phone-first users, by SMS. SMS is prepaid from the same wallet, and a Pro team can register its own alphanumeric sender ID so the code arrives under your name.
Bounces, complaints and unsubscribes land on a single list that transactional and marketing mail both honour, so a customer who left a campaign still gets their receipt and a bounced address is never sent to again.
Delivery, bounce, complaint, open and click events reach your server as signed HTTP POSTs, so an order system can mark a receipt delivered without polling.
5,000 emails a month and 200 a day, with no card and no end date. Pro is $15 a month for 50,000 emails, and in Kenya that price is billed in shillings from your wallet.
The API is the same one every Notix customer uses: a JSON body, a Bearer key, and an idempotency key so a retry never double-sends. Full reference on the email API page and in the docs.
curl -X POST https://app.usenotix.dev/api/v1/emails \
-H "Authorization: Bearer $NOTIX_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-4471-receipt" \
-d '{
"from": "receipts@acme.co.ke",
"to": "customer@example.com",
"subject": "Your receipt for order 4471",
"html": "<p>Thanks for your order.</p>"
}'
import { Notix } from "notix-js";
const notix = new Notix(process.env.NOTIX_API_KEY);
const { data, error } = await notix.emails.send(
{
from: "receipts@acme.co.ke",
to: "customer@example.com",
subject: "Your receipt for order 4471",
html: "<p>Thanks for your order.</p>",
},
{ idempotencyKey: "order-4471-receipt" },
);
from notix import Notix
client = Notix(os.environ["NOTIX_API_KEY"])
data, err = client.emails.send({
"from": "receipts@acme.co.ke",
"to": "customer@example.com",
"subject": "Your receipt for order 4471",
"html": "<p>Thanks for your order.</p>",
})
Billing is the main difference: the wallet, the shilling price list and the top-up methods above. Sending itself is the same JSON API and SMTP relay as everywhere else, and domain verification works the same way, with SPF, DKIM and DMARC records on your own domain.
SMS codes to Kenyan numbers go out under a sender ID. The shared Notix sender ID works on every plan; a Pro team can request its own alphanumeric sender ID of up to eleven characters, and Notix submits it to the network. Details, and the two-call flow for codes, are on the OTP use case page.
If your app already sends through SMTP, nothing about the code changes. The relay is smtp.usenotix.dev on port 465 with implicit TLS or port 587 with STARTTLS, the username is the word notix, and the password is your API key. Laravel, Rails and Django each take that as four lines of configuration, and the SMTP relay page has the settings for each. Messages sent that way appear in the same log, obey the same suppression list and fire the same webhooks as messages sent through the API.
Before you switch a domain over, run the free deliverability check on it. It reads the SPF, DKIM and DMARC records you have published and tells you what is missing, which is the same check the dashboard runs when you add the domain.
| Item | Limit | Where it is set |
|---|---|---|
| Recipients | 50 per message across to, cc and bcc; each one counts as an email | POST /v1/emails, and RCPT TO on the SMTP relay |
| Attachments | 10 files, 7 MB each, 10 MB per email | Request body, measured after base64 decoding |
| Batch | 100 messages per call, 40 MB of attachments across the batch | POST /v1/emails/batch |
| Idempotency key | 256 characters, kept 24 hours | Idempotency-Key header |
Billed in naira or shillings from a prepaid wallet, no dollar card needed, the same API and SMTP relay everywhere.
ProductPay in naira through HitchPay into a prepaid wallet; the price per email is the one the app bills with.
NotixA free plan with no card, and Pro at $15 a month for 50,000 emails. Only sent volume is metered.
ProductOne JSON API for transactional and marketing email: send, batch, schedule, webhooks, typed SDKs.
ProductPoint any framework's mailer at one host and port; the relay turns SMTP into the same tracked, suppressed send.
Use casesSend one-time codes by email or SMS with two API calls, with expiry, length and risk scoring handled for you.
Verify a domain, copy an API key, make one call. The free plan does not ask for a card, and Pro is billed from a wallet you top up in shillings.