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.
POST /v1/send answers 202 with the mail's id before any provider is contacted. From there an API mail takes the same path as SMTP mail: rules, routing, failover, the timeline, and the archive, which keeps the JSON request Mailway accepted. The response is the start of the record, not the end of the send.
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 console, in webhook events, and on the public viewer. Full request and response shapes live in the API reference, and the machine-readable contract is the OpenAPI specification — generate a typed client from it, or hand it to your coding agent.
Just POST it
The same pipeline — failover, timeline, archive — behind one JSON endpoint, for stacks where SMTP is awkward. Send with a fetch(), get back the same mail ID you'll see in the console, 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 rate limiter and the 429 carries Retry-After; hit the daily cap and its 429 says it resets at 00:00 UTC; hit a quota and the 402 names which one in a machine-readable error code.
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 HTTP 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, 465 and 587 outbound. The alternate ports mean your app sends from wherever it happens to run.
Your mailer config has
one block to change
Mailway is in private beta, and we onboard teams one at a time. Leave your email and we'll send your invite when it's your turn.