Quickstart: your first delivered email
Five steps, about five minutes. Every snippet is copy-paste: replace acme.eu with your domain and [email protected] with an inbox you can open.
01Sign up and copy your keys
2 minCreate an account. Right after signup the dashboard shows a test key (
env_test_) and a live key (env_live_) once. Copy both. You can make more under Settings, API keys.Two things unlock the live key: click the link in the verification email, and pay the one-time €5 sender verification (excl. VAT) when the dashboard asks. It keeps fraudulent senders off the shared sending infrastructure. Until then the live key gets
402 verification_fee_required; the test key works right away.02Prove your code works with the test key
30 secTest-mode sends are validated, get a real id and show up in your logs under the Test toggle, but never leave Envello. The domain check is skipped, so you can wire up your app before DNS is done.
Terminalexport ENVELLO_API_KEY=env_test_... curl -X POST https://api.envello.dev/emails \ -H "Authorization: Bearer $ENVELLO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": "Acme <[email protected]>", "to": "[email protected]", "subject": "It works", "html": "<p>Sent from the Envello quickstart.</p>" }'You get a 202 with the email id:
{ "id": "8f1c2a7e-...", "status": "queued" }03Verify your sending domain
2 to 3 minAdd the domain in the dashboard under Domains, or with the API. Envello sends from a subdomain,
mail.acme.euby default, so your apex domain's existing mail setup stays untouched. The response lists the DNS records to publish (SPF, DKIM and DMARC). Add them at your DNS provider.Terminalcurl -X POST https://api.envello.dev/domains \ -H "Authorization: Bearer $ENVELLO_LIVE_KEY" \ -H "Content-Type: application/json" \ -d '{ "domain": "acme.eu" }'Envello re-checks pending domains on its own. To check right away, call verify with the domain id from the response:
Terminalcurl -X POST https://api.envello.dev/domains/DOMAIN_ID/verify \ -H "Authorization: Bearer $ENVELLO_LIVE_KEY"Most DNS providers publish records within a few minutes. If yours is slower, this is the step that stretches past five minutes, and nothing else is waiting on it.
04Send a real email
30 secSame request, live key, and a
fromon the verified sending subdomain. TheIdempotency-Keyheader makes a retry safe: send the same key twice and you get the first response back instead of a second email.curlcurl -X POST https://api.envello.dev/emails \ -H "Authorization: Bearer $ENVELLO_LIVE_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: welcome-001" \ -d '{ "from": "Acme <[email protected]>", "to": "[email protected]", "subject": "Hello from Envello", "html": "<p>This one really arrives.</p>" }'Or with the Node SDK:
Terminalnpm install envellosend.mjsimport { Envello } from "envello"; const envello = new Envello(process.env.ENVELLO_LIVE_KEY); const sent = await envello.emails.send({ from: "Acme <[email protected]>", to: "[email protected]", subject: "Hello from Envello", html: "<p>This one really arrives.</p>", }); console.log(sent);05Check it arrived
10 secThe status moves from
queuedtosentonce the email is handed off for delivery. Webhooks tell you about deliveries, bounces and complaints as they happen.Terminalcurl https://api.envello.dev/emails/EMAIL_ID \ -H "Authorization: Bearer $ENVELLO_LIVE_KEY"
Next: the full API reference, every error code, or an SDK for your language.