Send and receive
Work with outbound email and inbound replies through the same inbox APIs.
A Mailgun alternative with the inbox built in.
Send, receive and inspect email through MailSlurp. Connect replies to your app and test the whole message journey before a release.
Trusted by teams at
Give every workflow an address of its own.
Create real email addresses in the dashboard or through the API. Receive replies, inspect messages and organize inboxes around your customers, applications and test environments.
Use MailSlurp domains or connect your own domain. Choose inbox lifetimes and retention settings to suit the workflow.
Explore programmable email
React to incoming messages
Use webhooks to notify your app when an email arrives, then retrieve its content and attachments.
Inspect what was delivered
Open the received message, headers and raw content when a workflow needs debugging.
Keep the received message within reach.
Look beyond the send event. Open an email in the dashboard, inspect its final content and use the API to retrieve the fields your application needs.
For invoices, orders and support messages, add AI extraction to turn email and attachment content into structured records.
Turn incoming email into data
Test the send before your customers depend on it.
Pair your email workflow with inbox placement testing, domain checks and device previews. Check where a test lands and how the message looks before releasing a new template or changing a sending service.
Check inbox placement
How to bring a workflow into MailSlurp
Create an inbox and connect your app
Start with an address in the dashboard, then use the MailSlurp API and SDK guides to create and manage inboxes from your application.
Send a representative message
Test the confirmation, receipt or reply your app depends on. Inspect the delivered email and verify any domain settings required for your sending path. Plans show the current sending allowances.
Automate the next action
Configure a webhook or wait for the expected email through the API. Check the content, extract the data you need and continue the workflow with a repeatable test.
Put inbound email beside your outbound workflow.
Follow the message and its reply
Create a dedicated address for a workflow and receive its replies in MailSlurp. Retrieve the body, headers and attachments through the API, or use a webhook to tell your application when a message arrives.
Map sending requests and inbound events
For a Mailgun migration, map your existing routes, send requests and event handlers to MailSlurp. Start with a representative message and reply, then add automated assertions and device previews. For campaign previews specifically, explore the Mailgun Inspect alternative. For a broader evaluation, see our Mailgun alternatives page.
Questions before you switch?
Can I migrate one Mailgun workflow at a time?
Yes. Start with one sender, recipient flow and inbound route. Map the send payload, reply handling and webhook events to MailSlurp, then check the actual delivered message and a representative reply. Configure the relevant domain records for the sending path and expand only after the first complete application flow works. Build the first send-and-reply flow.
Can I receive replies and attachments?
Yes. Create an inbox, receive email and retrieve its content, headers and attachments through the API. Use webhooks when your application needs to react to incoming messages.
Can I use SMTP as well as the API?
Yes. MailSlurp supports SMTP sending alongside inbox APIs. Use the connection settings for your inbox, send a representative message and verify the reply through a webhook or the API. The sending guide covers both SMTP and API setup. See SMTP sending setup.
Bring your next email workflow into MailSlurp.
Start with an inbox, a real message and the next action your app needs.
