Migrate from Postmark

Postmark and eusend have the same shape — an HTTP API for transactional email, an SMTP door for everything else, and webhooks for delivery events — so a typical migration is an afternoon, most of it waiting on DNS. What you gain is an EU-native provider: your mail is sent and stored on infrastructure in the EU, operated by a Norwegian company, with no US parent in the chain.

The code change

Install the SDK with npm install @eusend_dev/sdk. The main difference you'll notice is casing — Postmark's fields are PascalCase, eusend's are camelCase — and that eusend returns { data, error } instead of throwing on failure.

import postmark from 'postmark'

const client = new postmark.ServerClient(
  process.env.POSTMARK_SERVER_TOKEN
)

await client.sendEmail({
  From: 'Acme <[email protected]>',
  To: '[email protected]',
  Subject: 'Welcome',
  HtmlBody: '<p>Thanks for signing up.</p>',
  MessageStream: 'outbound',
})

import { Eusend } from '@eusend_dev/sdk'

const eusend = new Eusend(
  process.env.EUSEND_API_KEY
)

await eusend.emails.send({
  from: 'Acme <[email protected]>',
  to: '[email protected]',
  subject: 'Welcome',
  html: '<p>Thanks for signing up.</p>',
})

Field mapping

Batch sending maps one-to-one: client.sendEmailBatch([...]) becomes eusend.batch.send([...]), up to 100 messages per request. If you use Postmark templates, eusend has server-side templates too — pass templateId instead of a body; see the docs for the variable syntax.

If you send over SMTP

Anything pointed at Postmark's SMTP endpoint moves by swapping credentials — no code change. One thing to get right: eusend uses implicit TLS on port 465 (the connection is encrypted from the first byte); STARTTLS on 587 is not supported.

// Before: smtp.postmarkapp.com:587, server token as user and pass
// After — note the port: eusend is implicit TLS on 465, not STARTTLS on 587
const transport = nodemailer.createTransport({
  host: 'smtp.eusend.dev',
  port: 465,
  secure: true,
  auth: { user: 'eusend', pass: process.env.EUSEND_API_KEY },
})

Webhooks

Postmark gives each event type its own webhook; eusend sends all events to one endpoint and you subscribe to the types you want. The events map directly:

Where Postmark relies on HTTP basic auth or IP allowlists to protect the endpoint, every eusend webhook is signed with HMAC-SHA256 — verify the signature and you're done. The webhook docs show the exact scheme.

What's honestly different

• Attachments carry over. Postmark's Attachments array maps to eusend's attachments — rename Name → filename, Content → content (still base64), ContentType → content_type, and ContentID → content_id for inline images. Up to 20 files, 10 MB combined per message.
• Bring your suppression list. eusend suppresses hard bounces and complaints automatically, but it can't see Postmark's history. Export your suppression list and import the CSV before your first send, so addresses that already bounced don't get a fresh attempt from a new IP.
• Broadcast-stream traffic waits. Transactional sending is open today; bulk campaigns open as the platform warms. If you use Postmark's broadcast streams, plan that part for later.

Before you flip production

• Verify your sending domain and add its DKIM and DMARC records — the Domains page generates them. Sends from unverified domains are rejected.
• Migrate against an eu_test_ API key first — test sends are accepted and tracked but never delivered — then switch to eu_live_.
• Keep your Postmark account alive for a week or two after cutover so in-flight webhooks and your suppression export have somewhere to come from.