Eight guides, one for each stack, and the same three steps on every one: get an API key, send one email, and find it in the log. Pick yours below.
Three steps, in the same order, on every page: get an API key, send one email, then find it in the log. Whatever you build in between is yours, but those three steps and the two mistakes almost everyone makes on the first try are identical across every stack, so each guide below covers them the same way.
All eight talk to one thing: POST https://api.sendvia.io/v1/send, the same endpoint whether the request comes from a raw HTTP call or from a framework's own mail layer speaking SMTP to sendvia's relay. Laravel, Django and Ruby on Rails already have a first-class place to configure an SMTP server, so those three guides use it instead of hand-building a request. WordPress does the same, through whichever SMTP plugin your site already runs.
fetch, nothing installed.requests library.Mail facade, configured against sendvia's SMTP relay.send_mail(), configured against sendvia's SMTP relay.You need a sendvia account, which is free to create, and an AWS account of your own: sendvia sends through Amazon SES running inside your account, not its own, so there is a short setup on Amazon's side before the first email leaves. The SES setup guide covers that part screen by screen.
The free plan is enough to finish any guide here: 250 emails a day on 1 domain. The one limit that catches people earlier than that is Amazon's own: a new SES account starts inside a sandbox that only sends to email addresses you have verified yourself, and every guide's troubleshooting section covers exactly what that looks like and how to get past it. sendvia's full list of limits covers the rest of the ceilings, in case one of them matters before you begin.