SMTP relay · Email API
SMTP relay service and Email API for your apps
Send order confirmations, password resets and notifications from your website, WordPress, CRM or code through authenticated, monitored infrastructure. Pay per email with the same credits — no monthly plan.
1 credit = 1 email · suppressed addresses never charged · failed deliveries refunded
Host: smtp.inboxroads.com
Port: 587 (STARTTLS) · 465 (SSL/TLS) · 2525
Encryption: TLS required
Username: ir-xxxxxxxxxxxx
Password: •••••••••••••••••••••••••
From: you@your-verified-domain.comcurl -X POST https://inboxroads.com/api/v1/send \
-H "Authorization: Bearer $INBOXROADS_KEY" \
-H "Content-Type: application/json" \
-d '{"from":"Shop <orders@shop.com>",
"to":["jane@example.com"],
"subject":"Order #1024 confirmed",
"html":"<p>Thanks for your order!</p>"}'# .env
MAIL_MAILER=smtp
MAIL_HOST=smtp.inboxroads.com
MAIL_PORT=587
MAIL_USERNAME=ir-xxxxxxxxxxxx
MAIL_PASSWORD=your-smtp-password
MAIL_FROM_ADDRESS=orders@shop.comconst transporter = nodemailer.createTransport({
host: "smtp.inboxroads.com", port: 587, secure: false, // STARTTLS
auth: { user: "ir-xxxxxxxxxxxx", pass: process.env.SMTP_PASS },
});
await transporter.sendMail({ from: "orders@shop.com",
to: "jane@example.com", subject: "Welcome!", html: "<p>Hi</p>" });Everything transactional email needs
SMTP relay on 587, 465 and 2525
Standard SMTP with TLS and per-app credentials you can revoke individually. Works with any SMTP-capable software.
JSON Email API
Send HTML or text with attachments, tags and custom headers using your API key. Check status per message.
Your authenticated domain
Messages go out from your verified domain with SPF, DKIM and DMARC, keeping your brand and reputation consistent.
Message log
Search every message and see each recipient’s status: queued, sent, delivered, bounced, complained, failed.
Signed webhooks
Receive delivery, bounce and complaint events at your endpoint, signed with HMAC-SHA256.
Automatic suppression
Hard bounces and spam complaints are suppressed automatically so you stop sending to addresses that hurt deliverability.
Up and running in four steps
Create a free account
Verify your sending domain
Request SMTP access (reviewed quickly)
Create credentials and send
Every account is reviewed and starts with a daily sending limit that grows with a good sending record. That is how we keep delivery reliable for everyone on the platform.
SMTP relay FAQ
An SMTP relay accepts email from your website or application over SMTP and delivers it to recipients through managed sending infrastructure. Instead of running your own mail server, you point your app at smtp.inboxroads.com with a username and password.
Transactional and application email that recipients expect: order confirmations, receipts, password resets, account notifications and newsletters to people who signed up. Purchased lists and unsolicited email are not allowed under the acceptable use policy.
With the same prepaid credits as the rest of InboxRoads: 1 credit per recipient. There is no monthly subscription. Addresses on your suppression list are not charged, and emails that permanently fail are refunded.
Port 587 with STARTTLS (recommended), port 465 with SSL/TLS, and port 2525 with STARTTLS for networks that block 587. Authentication (PLAIN or LOGIN) is only accepted over an encrypted connection.
Yes. The From address must use a sending domain you have verified in InboxRoads with SPF, DKIM and DMARC. This protects your reputation and is required by Gmail and Yahoo for bulk senders.
Yes. Anything that can send through SMTP works — WordPress SMTP plugins, WooCommerce, Laravel, Node.js (Nodemailer), Python, PHPMailer, CRMs and help desks. Developers can also use the JSON Email API.
Guides: SMTP setup · Email API reference · Webhooks
Get your SMTP credentials
Create a free account, verify your domain and request SMTP access. Pay only for the emails you send.