Skip to content
EmBoux

EmBoux — Email Infrastructure API

Stop paying 1000% margins to B2C email providers for B2B problems. EmBoux is the API-First email plumbing you need to scale your software.

The Problem: You’re Using the Wrong Tool for Multi-Tenancy

Section titled “The Problem: You’re Using the Wrong Tool for Multi-Tenancy”

If you’re an Agency, ERP, or SaaS Developer handling email for dozens or hundreds of sub-clients, you know this pain:

Abusive Overage Pricing

Mailgun or SendGrid lure you with a base plan, then charge up to $1.10 per 1,000 extra emails. A disguised markup that devours your profitability.

Billing Amnesia

They retain your sending logs for only 3 to 7 days. When month-end comes and you need to bill Client X for their usage, the data is gone.

Noisy Neighbor Danger

If one of your clients gets hacked and fires 50,000 spam emails, traditional providers just send them — then hand you the surprise bill.

Manual Multi-Tenancy

Creating subaccounts, managing API keys per client, setting individual limits — all manual, all fragile, all your problem.


EmBoux is not just SMTP. It’s an Inbound/Outbound Email Orchestration Engine designed exclusively to run white-label beneath your application.

Instead of charging you penalties, we give you total control. We manage the servers and reputation; you focus on making money with your clients through our API.


Isolate each of your clients automatically. While other providers force you to manage subaccounts manually, the EmBoux API lets you define hard caps per domain from your own code.

The Benefit: You control your fixed costs. If a tenant gets hacked or has a bug in their code, EmBoux rejects the email at SMTP level before you have to pay the bill.

Terminal window
# Provision a new client with one API call
curl -X POST https://api.emboux.com/domains/ \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "client-company.com"}'
{
"id": 42,
"name": "client-company.com",
"created_at": "2026-03-15T10:30:00"
}

Each API key is scoped to a partner. Quotas — domains, mailboxes per domain, aliases per mailbox, storage, transfer — are enforced automatically at the infrastructure level. Learn more →


Pillar 2: Instant Suspension & Reactivation

Section titled “Pillar 2: Instant Suspension & Reactivation”

Protect your revenue by freezing service for non-paying clients without losing their data. One API call suspends mail delivery; another restores it instantly when they pay.

The Benefit: Automated grace periods with email reminders at days 7, 15, and 22. After 30 days, excess domains are suspended (most recent first). When the client pays or upgrades, everything reactivates automatically — zero manual intervention.

Terminal window
curl -X PUT https://api.emboux.com/domains/client-company.com/suspend \
-H "Authorization: Bearer YOUR_API_KEY"
{
"name": "client-company.com",
"suspended": true,
"message": "Domain suspended"
}

EmBoux immediately stops accepting mail for this domain. No data is deleted.

With the Odoo integration, the entire suspend → notify → reactivate cycle is fully automated based on subscription status. Full lifecycle docs →


Set how long emails are kept per domain. A server-side cron purges expired messages daily — no client action needed.

The Benefit: Offer tiered retention as part of your plans. Starter clients get 30 days, Enterprise gets 90. The infrastructure enforces it automatically.

Terminal window
# Set 90-day retention for a premium client
curl -X PUT https://api.emboux.com/domains/premium-client.com/retention \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"retention_days": 90}'

Combined with per-mailbox storage quotas, you get full capacity governance without manual monitoring. Storage & Quotas docs →


Everything is a REST call. No dashboards to click through, no tickets to open.

import requests
API = "https://api.emboux.com"
KEY = "Bearer YOUR_API_KEY"
# Full client provisioning in 3 calls
requests.post(f"{API}/domains/",
json={"name": "acme.com"},
headers={"Authorization": KEY})
requests.post(f"{API}/users/",
json={"domain_name": "acme.com",
"email": "[email protected]",
"password": "secure-pass"},
headers={"Authorization": KEY})
requests.post(f"{API}/aliases/",
json={"domain_name": "acme.com",
"source": "@acme.com",
"destination": "[email protected]"},
headers={"Authorization": KEY})

Full Python guide →


EmBouxTraditional Providers
Multi-tenancyNative — API keys scoped per partner with enforced quotasManual subaccounts, no hard limits
Overage protectionHard caps at infrastructure level — excess is rejected, not billedSend first, bill later — surprise invoices
Suspension controlOne API call, data preserved, instant reactivationOpen a support ticket and wait
Storage quotasPer-mailbox enforcement at server levelNot applicable (no inbound)
Email retentionConfigurable per domain, auto-purge cron3-7 day log retention, then gone
Pricing modelPredictable plans with included capacityPer-email pricing with hidden markups

Using Odoo? EmBoux ships with two native modules that handle everything automatically:

Zero-Code Provisioning

Customer buys a plan → API key created → quotas synced → welcome email sent. No manual steps.

Self-Service Portal

Customers manage domains, mailboxes, aliases, and API keys at /my/emboux. You don’t touch anything.

Automated Lifecycle

Grace periods, suspension, reactivation, overage billing — all triggered by subscription status changes.

Plans & Add-ons

Pre-built Starter / Business / Enterprise plans. Sell extra domains, mailboxes, and alias packs as add-ons.

Odoo Integration Guide →


1. Get your API key

From your Odoo portal at /my/emboux/api or from your account manager.

2. Create a domain

POST /domains/ — one call, immediately active.

3. Add mailboxes

POST /users/ — passwords securely hashed, ready for IMAP/SMTP.

4. Ship it

Your clients send and receive email. You bill them. Done.

Start the Quick Start guide →