Move a project to Minket
A project on the resend SDK moves by changing two environment variables; its code stays as it is.
A project on the resend SDK moves by changing two environment variables; its code stays as it is.
RESEND_BASE_URL=https://api.minket.com RESEND_API_KEY=minket_live_<your key>
import { Resend } from "resend";
const resend = new Resend(process.env.RESEND_API_KEY);
await resend.emails.send({
from: "receipts@mail.fernbank.example",
to: "rui.okafor@example.com",
subject: "Your receipt for order 10452",
html: "<p>Thanks, Rui.</p>",
});Each version runs against the API, error names and statuses included.
Paths keep Resend's spelling and answers keep its shapes, errors included.
{
"statusCode": 422,
"message": "Missing `to` field.",
"name": "validation_error"
}Deliveries are signed the svix way Resend uses, so resend.webhooks.verify accepts them with the new endpoint's secret.
svix-id svix-timestamp svix-signature
Each step can be undone by putting the two variables back, until the last one.
bounce. host differ, so both sets of records stay valid.minket_test_ key on a preview deployment and run every email path.POST /v1/suppressions and reason: "imported".It reads the base URL once, at import: set it before the first import.
Calls that write api.resend.com out need the host read from the same variable.
Every mirrored path and what differs.
Not on resend 6.12.4 or later: setting the two variables is enough.
No. Add each endpoint in Minket and use the secret it shows you.