Migrate to Anypost

Moving providers is mostly mechanical: swap the SDK, point your auth at an Anypost key, and reshape a request body or two. These guides walk through each switch provider by provider, with before-and-after code for every SDK and a full webhook event-name mapping.

You can run your current provider and Anypost in parallel during cutover; they are fully independent. Migrate one email type at a time and verify delivery before cutting over completely.

Every account starts with a free evaluation: build against the real API and send to your own verified domains while we get to know your sending. When you move your volume over, our deliverability experts warm up your sending as it moves, so mailbox providers see a steady sender, not a sudden new one.

From Amazon SES: Drop the AWS SDK, IAM, and SNS: one API key, a flat send body, and direct HTTP webhooks.
From Mailgun: Swap Basic auth + form-encoded requests for a Bearer token and JSON.
From Postmark: Rename PascalCase fields to lowercase, swap the auth header, and turn To into an array.
From Resend: A light migration: change the package and key, then flatten tags and adjust your webhook loop.
From SendGrid: Flatten the personalizations wrapper into a plain JSON body and remap webhook event names.
From SparkPost (Bird): Now Bird Email: switch to standard Bearer auth, flatten the nested body, and remap webhook events.

Don't see your provider yet? The concepts transfer, so start with the quickstart and the send-email reference, or browse the docs.