A small API with a complete record.
Send over HTTP with idempotency keys and batches; every response correlates to a timeline, the archive, and webhooks.
The send API is one endpoint — POST /v1/send — that accepts JSON, returns the mail's id, and feeds the same pipeline as SMTP: routing, failover, the timeline, the archive. Idempotency keys make retries safe (the same key returns the original send instead of a duplicate), and batches of up to 100 messages answer with a per-message 207 status.
Sends can be scheduled up to 72 hours ahead, routed per-request, and correlated end to end: the id in the response is the same id in the dashboard, in webhook events, and on the public viewer. Full request and response shapes live in the API reference.
Or just POST it
The same pipeline — failover, timeline, archive — behind one JSON endpoint, for stacks where SMTP feels like archaeology. Send with afetch(), get back the same mail ID you'll see in the dashboard, the public viewer, and the webhooks.
mw_test_… drives the sandbox, mw_live_… is production. No guessing which environment you just emailed.
Put an Idempotency-Key on the request and retry as hard as you like — a repeated key returns the original send instead of a duplicate.
Up to 100 messages per request, answered with a 207 and a per-message status — you know exactly which ones made it.
Hit the monthly quota and the 429 comes with a Retry-After header and a machine-readable error code. Not vibes.
live on api.mailway.net · sandbox on api.mailway.dev
No SDK.
That's a feature.
It's standard SMTP — Nodemailer, smtplib, Laravel's mailer, ActionMailer and net/smtp already speak it fluently. Nothing to install today, nothing to rip out later. Prefer HTTP? The REST API comes with bearer auth, idempotency keys, and batch send.
- Change one config block. Ship. That was the migration.
- TLS on every connection — STARTTLS and implicit TLS.
- Staging that can't email your customers — point it at
smtp.mailway.devand everything is captured, nothing is delivered until you explicitly release it.
GCP blocks port 25 outright. DigitalOcean blocks 25, 465and 587 outbound. The alternate ports mean your app sends from wherever it happens to run.
Your mailer config has
one line to change
Mailway is in private beta — we onboard teams one at a time. Leave your email and we'll send your invite when it's your turn.