REST API and SMTP relay
One call from your backend, or the SMTP relay for CMSs and shops that only speak SMTP.
-
POST /v1/send - SMTP relay on port 587 with STARTTLS
- Separate Live and Sandbox environments
Pre-launch Nilomail isn’t live yet: we’re only collecting the waitlist. Join with your email and we’ll let you know when access is available. Join the waitlist →
API & transactional email
The emails that can’t fail, behind a clean API.
Order confirmations, password resets and notifications from noreply@, via REST API or SMTP relay. With logs, webhooks and authenticated domains, in the same service as your mailboxes.
API keys under control
Each service gets its own key with only the permissions it needs.
- Per-key scopes
- IP allowlists for production
- Zero-downtime key rotation
Webhooks for every event
Know in real time what happens to your messages and react in your own system.
-
email.delivered,email.bounced,email.complaint -
email.opened,email.clicked - Send test events
Logs and domains
Every message is traceable, and every domain is authenticated.
- Message log with header inspector and resend
- DKIM keys and custom Return-Path
- Separate streams for transactional and conversational mail
When it is not a fit
- If you only need very high-volume sending, without mailboxes or newsletters: specialised sending-only services exist for that.
Frequently asked questions
Can I use the SMTP relay to read mail?
No. The SMTP relay is only for sending from your applications. Mail is read in the Nilomail app.
Can I keep clients separate?
Yes. Each client gets a workspace with its own domains, API keys and sending reputation.