Envello
Sweego alternative

Switching from Sweego? Move your transactional email to Envello

A step-by-step guide: DNS setup alongside your existing records, the sending-code swap, a dual-send cutover window, and verification with 90 days of searchable logs on Pro.

Sweego sends email through POST https://api.sweego.io/send with an Api-Key header. Because the same endpoint serves several channels, every request names channel and provider, and the content fields are kebab-case (message-html, message-txt, reply-to). Envello's /emails endpoint is email only, with snake_case fields and a Bearer key. The send call is a reshape; variables with several recipients and the bulk endpoint are the parts that need a decision.

Before: Sweego fetch
await fetch("https://api.sweego.io/send", {
  method: "POST",
  headers: {
    "Api-Key": process.env.SWEEGO_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    channel: "email",
    provider: "sweego",
    recipients: [{ email: "[email protected]" }],
    from: { name: "Acme", email: "[email protected]" },
    subject: "Welcome",
    "message-html": renderedHtml,
  }),
});
After: Envello fetch
import { Envello } from "envello";

const envello = new Envello(process.env.ENVELLO_API_KEY);

await envello.emails.send({
  from: "Acme <[email protected]>",
  to: "[email protected]",
  subject: "Welcome",
  html: renderedHtml,
});
Before: Sweego REST
curl -X POST https://api.sweego.io/send \
  -H "Api-Key: $SWEEGO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "email",
    "provider": "sweego",
    "recipients": [{ "email": "[email protected]" }],
    "from": { "name": "Acme", "email": "[email protected]" },
    "subject": "Welcome",
    "message-html": "<p>Welcome aboard</p>"
  }'
After: Envello REST
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": "Welcome",
    "html": "<p>Welcome aboard</p>"
  }'
Field mapping

Sweego fields and their Envello equivalents

SweegoEnvello
Api-Key: <API key>Authorization: Bearer <API key>
channel: "email", provider: "sweego"Not needed; POST /emails is email only
from: { email, name }from: "Name <email>"
recipients: [{ email, name }]to (string or array of "Name <email>")
reply-to: { email, name }reply_to
subject, message-html, message-txtsubject, html, text
headersheaders (map)
list-unsubheaders: List-Unsubscribe and List-Unsubscribe-Post, or stream: "broadcast", which adds an unsubscribe link for you
attachments: [{ filename, content }]attachments: [{ filename, content (base64), contentType }]
campaign-id, campaign-tagstags: [{ name, value }]; for example campaign-id "welcome" becomes { name: "campaign", value: "welcome" } (letters, digits, _ and - only)
campaign-type: "transac" or "newsletter"stream: omit it for transactional, "broadcast" for updates to your own users
template-id + variablestemplate_id + variables for plain {{variable}} templates
POST /send/bulk/email (per-recipient variables)POST /emails/batch with one fully formed email per recipient, up to 100 per call
dry-run: trueA test-mode API key: the request is validated but nothing is delivered

Variables and several recipients

Sweego's /send applies variables only when there is one recipient, and points you at /send/bulk/email for personalised copies. Envello splits it the same way: a template send goes to the addresses in to, and personalised copies go through POST /emails/batch, one complete email per recipient.

Templates

Sweego templates use {{ name }} placeholders. Envello's stored templates use {{name}} with flat string values, so plain templates carry over with little change. Render anything with logic in your own code and send it as html.

Webhooks

Point your event consumer at Envello's webhook format: one JSON event per request (delivered, bounced, complained, opened, clicked), signed with Envello-Signature: t=<unix seconds>,v1=<hex>, an HMAC-SHA256 over the timestamp, a dot and the raw body. Map Sweego's event names to those five before you write the new handler.

Four steps

The migration, end to end

1. Add Envello DNS records alongside your existing Sweego records

Verify your sending domain in Envello and add the SPF include, DKIM CNAMEs, and the return-path CNAME Envello generates. Keep your existing records in place: both providers can authenticate the same domain at once, which is what makes a safe cutover possible. Only remove the old records after Envello has been the sole sender for a few days.

2. Swap the sending call

Point your outbound path at Envello's SDK. The request shape (from, to, subject, html, text, cc, bcc, reply_to, headers, attachments) mirrors the common transactional-API pattern, so the diff in most codebases is the import line, the client instantiation, and the API key environment variable. Templates rendered client-side (React Email, MJML, plain string) plug straight into the html field.

3. Dual-send during the cutover window

Route a small percentage of traffic to Envello first, or fork production sends so each message goes through both providers to non-critical recipients while you verify. Envello's log search shows every send, bounce, complaint, open, and click for 90 days on Pro (7 days on Free, up to 365 days on Scale) so you can confirm parity before flipping the rest of the traffic.

4. Cut over and retire Sweego

Once Envello has handled a full week of production traffic without regressions on your key deliverability metrics (bounce rate, complaint rate, delivered rate per domain), route 100% of sends through Envello. Export your Sweego suppression list and add each address with Envello's POST /suppressions so previously-suppressed recipients stay suppressed. Remove the old DNS records last.

Sending HTML from React components? See the React Email guide for how render() plugs straight into the html field.

FAQ

Migration questions

Can I keep sending through Sweego while I test Envello?+

Yes. Both providers authenticate the same domain via separate DKIM selectors and their own SPF include, so parallel sending is safe as long as each provider's records are in place. Keep the old records until Envello has been the sole production sender for a few days, then remove them.

What happens to my suppression list?+

Export it from Sweego and add each address with POST /suppressions (a full-access API key works, one address per request), or one by one in the dashboard. If you skip this step, addresses that Sweego had marked as bounced or complained can send successfully through Envello on day one and generate the same bounce or complaint again, which harms deliverability. Import first, cut over second.

Do I need to change my webhook consumer?+

Yes, at least the payload shape. Envello's webhooks send delivered, bounced, complained, opened, and clicked events with HMAC-signed payloads; the field names and signature header are documented at envello.dev/docs. If your current consumer branches on your existing provider's specific bounce-subtype taxonomy, decide upfront how each subtype maps to Envello's simpler event set before writing the new handler.

How long does the whole migration take?+

For a codebase with a single central sending path, most teams complete the code change in under an hour. Add DNS propagation (up to 48 hours, usually much less), a dual-send verification window (a few days), and one week of production monitoring before retiring the old provider. Plan for two to three weeks end-to-end, not one afternoon.

Free tool

Check your own GDPR/DPA gaps before you switch

8 questions covering data residency, retention, and subprocessor documentation, the same things a security questionnaire asks.

Run the free checklist →
Ready to migrate?

Create your account and migrate at your own pace.