Switching from AhaSend? 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.
AhaSend's API v2 sends through POST https://api.ahasend.com/v2/accounts/{account_id}/messages with a Bearer key. The account ID sits in the path, from is an object, recipients is an array where each address becomes its own message, and the body fields are html_content and text_content. AhaSend states that it stores message data in the EU, so data location alone isn't a reason to move. The send call is a reshape; substitutions and per-recipient sends are the parts that need a decision.
import { AhaSendClient } from "@ahasend/sdk";
const ahasend = new AhaSendClient({
apiKey: process.env.AHASEND_API_KEY,
accountId: process.env.AHASEND_ACCOUNT_ID,
});
await ahasend.messages.send({
from: { email: "[email protected]", name: "Acme" },
recipients: [{ email: "[email protected]" }],
subject: "Welcome",
html_content: renderedHtml,
});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,
});curl -X POST "https://api.ahasend.com/v2/accounts/$AHASEND_ACCOUNT_ID/messages" \
-H "Authorization: Bearer $AHASEND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": { "email": "[email protected]", "name": "Acme" },
"recipients": [{ "email": "[email protected]" }],
"subject": "Welcome",
"html_content": "<p>Welcome aboard</p>"
}'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>"
}'AhaSend fields and their Envello equivalents
| AhaSend | Envello |
|---|---|
| {account_id} in the URL path | Not needed; the API key identifies the account |
| from: { email, name } | from: "Name <email>" |
| recipients: [{ email, name }] (one message each) | to; for one email per recipient, POST /emails/batch with up to 100 emails |
| Conversation messages with cc and bcc | cc, bcc on POST /emails |
| subject, html_content, text_content | subject, html, text |
| reply_to | reply_to |
| headers | headers (map) |
| attachments: [{ file_name, data, base64, content_type }] | attachments: [{ filename, content (base64), contentType }] |
| attachments[].content_id (inline images) | No inline attachment field; host the image and link it from the HTML |
| substitutions (request or per recipient) | template_id + variables for plain {{variable}} templates; otherwise render the HTML in your code and send it as html |
| Template messages (stored transactional templates) | template_id + variables |
| tags (array of strings) | tags: [{ name, value }]; for example "welcome" becomes { name: "type", value: "welcome" } (letters, digits, _ and - only) |
| schedule.first_attempt (RFC 3339) | send_at (ISO 8601 with an offset) |
| retention (per message) | No per-message setting; retention follows your plan (7 days Free, 90 days Pro, configurable up to 365 on Scale) |
| sandbox: true | A test-mode API key: the request is validated but nothing is delivered |
One request, one message per recipient
AhaSend turns each entry in recipients into its own message and returns a result per recipient, with optional per-recipient substitutions. Envello sends one email to everyone in to. For one email per recipient, render each one in your code and post up to 100 to POST /emails/batch, which also returns a result per item.
Templates
AhaSend runs every message through its template engine, which understands {{ name }} placeholders and block tags. Envello's stored templates do {{variable}} substitution only, with flat string values. Plain placeholders carry over; anything with logic is easier to render in your own code and send as html.
Webhooks
AhaSend's SDK ships a WebhookVerifier for its signed deliveries. Envello sends Envello-Signature: t=<unix seconds>,v1=<hex>, an HMAC-SHA256 over the timestamp, a dot and the raw body. Replace the verifier and map AhaSend's event names to Envello's five (delivered, bounced, complained, opened, clicked).
The migration, end to end
1. Add Envello DNS records alongside your existing AhaSend 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 AhaSend
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 AhaSend 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.
Migration questions
Can I keep sending through AhaSend 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 AhaSend 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 AhaSend 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.
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 →