Send over SMTP today — a REST API is on the way. Drop in your credentials
and start sending — no complex configuration required.
SMTP today, REST API soon
SMTP relay works from any stack right now; a REST API is in development. Same account, same dashboard.
Your domains
Send from your own domains with DKIM and SPF configured automatically.
AI agent ready
MCP server, Agent Skills, and machine-readable docs for AI-native workflows.
REST API — coming soon. Send over SMTP today; this preview shows the API that's shipping shortly.
curl -X POST https://api.mailertogo.com/api/v1/emails \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "you@yourdomain.com",
"to": "user@example.com",
"subject": "Hello from Mailer To Go",
"html": "<p>You are up and running.</p>"
}'
import requests
requests.post(
"https://api.mailertogo.com/api/v1/emails",
headers={"Authorization": "Bearer YOUR_API_KEY"},
json={
"from": "you@yourdomain.com",
"to": "user@example.com",
"subject": "Hello from Mailer To Go",
"html": "<p>You are up and running.</p>",
},
)
fetch("https://api.mailertogo.com/api/v1/emails", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
from: "you@yourdomain.com",
to: "user@example.com",
subject: "Hello from Mailer To Go",
html: "<p>You are up and running.</p>",
}),
});
require "net/http"
require "json"
uri = URI("https://api.mailertogo.com/api/v1/emails")
req = Net::HTTP::Post.new(uri)
req["Authorization"] = "Bearer YOUR_API_KEY"
req["Content-Type"] = "application/json"
req.body = {
from: "you@yourdomain.com",
to: "user@example.com",
subject: "Hello from Mailer To Go",
html: "<p>You are up and running.</p>"
}.to_json
Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(req) }
Why developers choose Mailer To Go
Built for developers
SMTP relay, webhooks, and inbound routing today — with a REST API in development.
No bloated dashboards or marketing features you don't need.
Your domains, your reputation
Send from your own domains with DKIM, SPF, and DMARC
authentication configured automatically.
Secure and compliant
SSL/TLS encryption, data encrypted at rest.
GDPR compliant. Your data stays yours.
Zero to sending in seconds
Provision and start sending immediately. No server management,
no infrastructure to maintain. We handle everything.
Scales with you
From 25,000 emails on Starter to unlimited on Enterprise. Distributed,
fault-tolerant infrastructure that grows as you do.
Real support from real people
Chat support on every plan. No ticket queues,
no waiting days for a response.
Security and protection
We use SSL/TLS encryption on all our websites and
microservices satisfying the highest security and data
protection standards.
The data you store on Mailer To Go is encrypted in transit
and at rest on the server side.
Our mailing infrastructure is hosted on
DigitalOcean's SOC 2 Type II certified data centers.
Firewalls restrict access to our network from external
networks and between systems internally.
Backend access is limited to Mailer To Go staff and
requires key authentication and multi-factor
authentication.
Security
We understand the sensitivity of your data and we take all the
necessary steps to safeguard it. Keeping our services secure is
fundamental to the nature of our business. That's why security
is our number one priority.
Deep-dive guides on every RFC behind email — SMTP, DKIM, SPF,
DMARC, MIME, TLS, and more. Built for developers who want to
understand what happens under the hood.
Amazon SES's $0.10/1,000 sticker price only covers raw sending. Add the dashboards, event pipeline (SNS/SQS/Lambda/CloudWatch), and anti-abuse tooling you must build yourself, and the fully-loaded cost reaches ~$4-6/1,000 — a methodical total-cost-of-ownership breakdown.
Migrate from Postmark to Mailer To Go without losing deliverability: authenticate your domain, swap SMTP credentials, carry over your suppression streams, and cut over gradually with a rollback plan.
Migrate from Amazon SES to Mailer To Go without losing deliverability: authenticate your domain, swap SES SMTP/API credentials, carry over your suppression list, and cut over gradually with a rollback plan.