How to Switch from Resend to SMTPfast in 5 Minutes

Why Switch?

SMTPfast offers a Resend-compatible API, so you can migrate without rewriting your email integration. You get the same developer experience with competitive pricing and full delivery tracking.

Before and After

Before (Resend with fetch)

const res = await fetch("https://api.resend.com/emails", {
  method: "POST",
  headers: {
    Authorization: "Bearer re_your_resend_key",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    from: "[email protected]",
    to: "[email protected]",
    subject: "Welcome!",
    html: "<h1>Hello!</h1>",
  }),
});

const { id } = await res.json();

After (SMTPfast)

const res = await fetch("https://smtpfa.st/api/v1/emails", {
  method: "POST",
  headers: {
    Authorization: "Bearer sf_your_smtpfast_key",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    from: "[email protected]",
    to: "[email protected]",
    subject: "Welcome!",
    html: "<h1>Hello!</h1>",
  }),
});

const { id } = await res.json();

That is it. Two values changed: the base URL and the API key. Everything else stays the same.

Using the Resend Node SDK?

If you are using the Resend SDK, you can point it at SMTPfast by overriding the base URL:

import { Resend } from "resend";

const resend = new Resend("sf_your_smtpfast_key");

// Override the base URL to point to SMTPfast
resend.baseUrl = "https://smtpfa.st/api/v1";

await resend.emails.send({
  from: "[email protected]",
  to: "[email protected]",
  subject: "Welcome!",
  html: "<h1>Hello!</h1>",
});

Or use a simple fetch wrapper if you prefer not to depend on the Resend SDK at all.

Compatible Fields

SMTPfast accepts all the common Resend email fields:

Response Format

SMTPfast returns a Resend-compatible response:

{ "id": "clxyz123abc" }

You can retrieve full delivery details with GET /emails/:id, which returns Resend-compatible fields like last_event, from, to, subject, html, text, and created_at.

Retrieving Email Status

const res = await fetch("https://smtpfa.st/api/v1/emails/clxyz123abc", {
  headers: { Authorization: "Bearer sf_your_smtpfast_key" },
});

const email = await res.json();
// email.last_event -> "delivered"
// email.created_at -> "2026-04-07T12:00:00.000Z"

Migration Checklist

1. Create an SMTPfast account at smtpfa.st
2. Add and verify your sending domain in the SMTPfast dashboard
3. Generate an API key with email:send scope
4. Replace your base URL from https://api.resend.com to https://smtpfa.st/api/v1
5. Replace your API key from re_... to sf_...
6. Test by sending a single email and confirming delivery

The whole process takes about 5 minutes. Your existing code, payload structure, and response handling all stay the same.

What About Webhooks?

SMTPfast supports delivery webhooks for events like delivered, bounced, opened, and clicked. The webhook payload format may differ slightly from Resend. Check the API docs for details on configuring webhooks.