For developers
Send email from your app. Know what happened.
Password resets, sign-up confirmations, notifications: one POST request or your SMTP settings. Sent from your own domain, with an email log and automatic bounce suppression.
curl -X POST "https://www.obanox.com/api/v1/your-newsletter/send" \
-H "Content-Type: application/json" \
-H "API-KEY: $OBANOX_API_KEY" \
-H "API-SECRET: $OBANOX_API_SECRET" \
-d '{
"from": "[email protected]",
"to": "[email protected]",
"subject": "Reset your password",
"text": "Here is your link: …"
}'
# 202 Accepted
{ "id": 4711, "status": "queued" }
await fetch('https://www.obanox.com/api/v1/your-newsletter/send', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'API-KEY': process.env.OBANOX_API_KEY,
'API-SECRET': process.env.OBANOX_API_SECRET,
},
body: JSON.stringify({
from: '[email protected]',
to: '[email protected]',
subject: 'Reset your password',
text: 'Here is your link: …',
}),
});
// 202 Accepted
{ "id": 4711, "status": "queued" }
$ch = curl_init('https://www.obanox.com/api/v1/your-newsletter/send');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Content-Type: application/json',
'API-KEY: ' . getenv('OBANOX_API_KEY'),
'API-SECRET: ' . getenv('OBANOX_API_SECRET'),
],
CURLOPT_POSTFIELDS => json_encode([
'from' => '[email protected]',
'to' => '[email protected]',
'subject' => 'Reset your password',
'text' => 'Here is your link: …',
]),
]);
curl_exec($ch);
// 202 Accepted
{ "id": 4711, "status": "queued" }
requests.post(
"https://www.obanox.com/api/v1/your-newsletter/send",
headers={
"API-KEY": os.environ["OBANOX_API_KEY"],
"API-SECRET": os.environ["OBANOX_API_SECRET"],
},
json={
"from": "[email protected]",
"to": "[email protected]",
"subject": "Reset your password",
"text": "Here is your link: …",
},
timeout=10,
)
# 202 Accepted
{ "id": 4711, "status": "queued" }
“I never got the reset email.”
Sending an email is one line of code. Knowing whether it arrived, and keeping your domain’s reputation clean, is the part that eats your afternoon.
DNS before the first email
DKIM, SPF, a bounce domain, DMARC: get one record wrong and your emails land in spam.
Bounces you never see
A typo in a sign-up address, and you keep sending to a mailbox that doesn’t exist. Mailbox providers notice.
No record when support asks
When a user says nothing arrived, you dig through logs instead of looking it up.
Everything around the send call
You write the email. Obanox handles what happens after it leaves your app.
POST /send
REST API
One recipient per request, JSON in, 202 back. Emails are queued and usually go out within seconds.
SMTP
SMTP relay
For frameworks and tools that speak SMTP. Also supports attachments, Cc and Bcc.
DKIM · SPF · DMARC
Your own domain
Emails come from your domain, signed with DKIM, with their own bounce domain and DMARC reports.
recipient_suppressed
Bounce suppression
Hard bounces, spam complaints and undeliverable addresses are blocked automatically.
sent · bounced · complaint
Email log
Every email with its status. Search by recipient or subject and open what the user received.
awaiting_approval
Approval if you want it
Optionally hold emails until someone approves them, e.g. while testing a new integration.
Sender domain
Your domain, set up properly.
Add your domain and Obanox shows you exactly which DNS records to publish. It checks them on its own and tells you when they’re verified.
- DKIM signing with three CNAME records.
- Your own bounce domain with MX and SPF, so SPF aligns with your domain.
- A DMARC record and readable DMARC reports: see how Gmail, Outlook and others rate your domain.
Errors
Errors that tell you what to do.
Every error is JSON with a status code and a clear message. And the rule for retries is simple.
- 202
- Accepted and queued. Temporary problems on the recipient’s side are retried for you.
- 4xx
- Fix the request; sending it again unchanged won’t help.
- 429 · 5xx
- The only ones worth retrying later.
Three steps to your first email
No SDK to install. If your stack can send an HTTP request or speak SMTP, you’re ready.
-
1
Verify your domain
Publish the DNS records shown in your account, then request sending approval. We usually reply within a few hours.
-
2
Create an API key
Named keys, each revocable on its own. The same key and secret also work for SMTP.
-
3
Send your first email
POST to /send or enter the SMTP details in your framework. Then watch it appear in the log.
Your newsletter runs on the same account
Same domain, same suppression list, same API key. When you need more than transactional email, it’s already there.
Questions
Which plan do I need?
The API and the SMTP relay are part of these plans: Pro, Business. Pro starts at 24 € per month. Pricing
API or SMTP?
Use the API for one email per request with a JSON response. Use SMTP if your framework already sends through SMTP, or if you need attachments, Cc or Bcc. Both share domains, limits and the suppression list.
Is sending synchronous?
No. A 202 means the email was accepted and queued. It usually goes out within seconds, and temporary problems on the recipient’s side are retried automatically.
What happens when an address bounces?
Hard bounces, spam complaints and undeliverable addresses are blocked automatically. Further emails to them return recipient_suppressed, so your app can ask the user for another address.
Do transactional emails count towards my plan?
Yes, together with your newsletter emails. You get an email at 80 % and 100 % of your monthly emails.
Is there an SDK?
No, and you won’t need one: it’s a single JSON request. The documentation has copy-ready examples for cURL, PHP, Node.js and Python. Email API documentation
Ship the email feature. Skip the email infrastructure.
REST API, SMTP relay and email log in the Pro plan, from 24 € per month.