Migrate
Switch your email API to Sendpository
Field-by-field guides for moving from the email provider you use today, with the code on both sides.
In short
Moving an email API comes down to four changes: verify your domain with the new provider, swap the send call and API key, update your webhook handler for the new signature and event names, and map error handling to the new error types. Each guide below covers all four for one provider, then lists what to test before you switch production.Or let your coding agent do it
Paste it in. It works out which provider you use, rewrites every send and your webhook handler, and switches over behind a flag you can flip back.
Show the promptHide the prompt
Switch this project's email to Sendpository. First run `npx sendpository@latest init` - it opens my browser for me to approve, saves the API key and installs the Sendpository skill - then follow the skill's migration guide (references/migrate.md). If you can't run commands, read https://www.sendpository.com/agents/sendpository/references/migrate.md instead.
Migrate from Resend
Usually under an hour for the code, plus DNS propagation.
Migrate from SendGrid
An afternoon for most codebases - the request shape is the main rewrite.
Migrate from Postmark
An hour or two - the request maps field for field.
Migrate from Mailgun
An afternoon - mostly swapping form-data for JSON.
Migrate from Amazon SES
A day if you also retire SNS topics, SQS queues and bounce-processing Lambdas; an hour for the send call alone.
Send your first email in minutes
6,000 emails a month (up to 200 a day), free forever. No card needed.