SMTP Relay
For frameworks and platforms that can’t easily call our REST API, use the SMTP relay. Same DKIM signing, suppression, billing, and webhook delivery — your app just speaks plain SMTP.
Connection
| Setting | Value |
|---|---|
| Host | smtp.splashifypro.com |
| Port | 587 (STARTTLS) or 465 (TLS) |
| Username | emailapikey (literal) |
| Password | pk_live_... (your API key) |
TLS is required. Plain-text auth is rejected.
Test with swaks
swaks --to customer@example.com \
--from hello@yourcompany.com \
--server smtp.splashifypro.com \
--port 587 -tls \
--auth-user emailapikey \
--auth-password "$SPLASHIFY_API_KEY" \
--header "Subject: Test from swaks" \
--body "Hello"WordPress (WP Mail SMTP)
- Plugin → WP Mail SMTP → install
- Mailer → Other SMTP
- Host:
smtp.splashifypro.com· Port:587· Encryption:TLS - Auth: ON · Username:
emailapikey· Password: your API key - Save & send a test email
Django
# settings.py
EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"
EMAIL_HOST = "smtp.splashifypro.com"
EMAIL_PORT = 587
EMAIL_USE_TLS = True
EMAIL_HOST_USER = "emailapikey"
EMAIL_HOST_PASSWORD = os.environ["SPLASHIFY_API_KEY"]
DEFAULT_FROM_EMAIL = "hello@yourcompany.com"Laravel
MAIL_MAILER=smtp
MAIL_HOST=smtp.splashifypro.com
MAIL_PORT=587
MAIL_USERNAME=emailapikey
MAIL_PASSWORD=${SPLASHIFY_API_KEY}
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=hello@yourcompany.comNode (nodemailer)
import nodemailer from "nodemailer";
const transport = nodemailer.createTransport({
host: "smtp.splashifypro.com",
port: 587,
secure: false, // STARTTLS
auth: {
user: "emailapikey",
pass: process.env.SPLASHIFY_API_KEY,
},
});
await transport.sendMail({
from: "hello@yourcompany.com",
to: "customer@example.com",
subject: "Hello",
html: "<p>Welcome</p>",
});Postfix
In /etc/postfix/main.cf:
relayhost = [smtp.splashifypro.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_use_tls = yes
smtp_tls_security_level = encryptIn /etc/postfix/sasl_passwd:
[smtp.splashifypro.com]:587 emailapikey:pk_live_...postmap /etc/postfix/sasl_passwd
chmod 600 /etc/postfix/sasl_passwd*
postfix reloadThings to know
- From-domain still has to be verified. Same rule as the REST API — sends from unverified domains are rejected.
- Suppression list applies. Recipients on your account suppression list are silently dropped.
- Billing is identical. ₹0.01/email, first 200/day in sandbox are free.
- Webhooks fire normally. SMTP and REST sends produce the same event stream into your configured destinations.
- Per-message metadata via headers. Set
X-Configuration-Set: <name>on the outbound message to attribute the send to a config set.