MailSlurp FAQ

Email testing checks that your application sends the right message to the right recipient and that its links, codes, content and attachments work. MailSlurp gives automated tests real inboxes to receive those messages. Device rendering checks their appearance; inbox placement testing checks whether they arrive in the inbox or spam folder. Explore the documentation.

Create an inbox through the API, give its address to your application, trigger an email, then wait for a matching message and assert its contents. MailSlurp supports HTTP requests and SDKs, so the same workflow can run in local tests or CI without a person opening an email account. Start with the API.

Yes. MailSlurp creates real email addresses that can receive messages from your application and external senders. You can create separate inboxes for test runs, users or environments. Choose the inbox type and expiry settings for your workflow; keep an inbox if a later test needs the same address. Create and manage inboxes.

Yes. Use an inbox to send email, receive replies, read message bodies and headers, and download attachments. You can also inspect sent messages. Sending capacity and access depend on your plan, inbox configuration and sender settings. Read the email API guide.

Send your application's verification or password-reset message to a MailSlurp inbox. Wait for a message matching the expected recipient, sender or subject, extract the code or link, then use it in your browser or API test. Assert that the resulting login, verification or password change succeeds. Wait for the right message.

Yes. Create a MailSlurp inbox in your test, enter its address in the application, trigger the email and retrieve it with an SDK or HTTP request. Use the extracted link or code to continue the browser test. Give parallel tests separate inboxes or matching rules so they do not consume each other's messages. Find SDKs and testing examples.

Yes. MailSlurp supports linked Gmail and Outlook accounts, as well as connections to other mail servers. Authorize the account and configure the connection before using its inbox or sender. The available read, sync and sending operations depend on the connection and the permissions granted by the provider. Connect an existing mailbox.

Yes. You can use MailSlurp's supported IMAP and SMTP access for compatible inboxes, or connect an existing mail server with its IMAP and SMTP settings. SMTP sends mail; IMAP accesses received mail. Check the inbox type and connection instructions before choosing credentials or server settings. See IMAP and SMTP setup.

Yes. MailSlurp rents real phone numbers through multiple providers, including non-VoIP options. The current catalogue lists non-VoIP options for Australia, United Kingdom, and United States. Choose a number explicitly marked non-VoIP if that is required. A real number is not automatically non-VoIP, and no number guarantees acceptance by every third-party verification service. Choose a phone number.

The current phone catalogue includes Australia, Canada, Estonia, Finland, Israel, Netherlands, Poland, Sweden, United Kingdom, and United States. Number types, stock and sending or receiving capabilities vary by country and provider. The number picker shows the options available to your account before you rent; a country appearing in the catalogue does not guarantee immediate inventory. View phone number setup.

Yes, where the selected country and number support the required direction. Check the number's sending and receiving capabilities before renting it. Provider rules, destination restrictions, account permissions and usage limits also apply. Use the SMS API to send supported messages and retrieve incoming replies. Use the SMS API.

Rent a compatible phone number, enter it in your application's verification flow, trigger the SMS and wait for the matching message through MailSlurp. Extract the code and submit it in your test. Test applications and accounts you control; external services may restrict automated verification or reject particular number types. Test incoming SMS.

Yes. Your test can use an existing rented number, trigger a message, then wait for a matching SMS and assert its sender and body. Use unique message content or matching rules to isolate concurrent tests. Keep provisioning separate from each test when you need a stable number. Wait for an SMS in a test.

Yes. Keep a rented number for repeatable tests while its rental remains active, or release it when you no longer need it. Review the applicable rental and renewal terms before release. Do not assume a released number can be recovered or that its previous verification accounts transfer with it. Manage rented numbers.

Yes. MailSlurp can notify your application when an SMS arrives. Configure the supported SMS webhook event, verify incoming webhook requests and handle retries safely. Your application can then process the message or continue a workflow without repeatedly polling for new SMS. Configure webhooks.

Sending and receiving are separate capabilities. A number or country may support one direction, and provider or destination rules can add further restrictions. Check the selected number's capabilities and any sending requirements before building a two-way workflow. Receiving a message successfully does not establish that outbound sending is enabled. Check phone capabilities.

Email rendering testing captures how an email actually appears in email apps and devices. It helps you find layout, font, image and dark-mode differences that a browser preview can miss. MailSlurp produces screenshots so you can compare the same message across your selected targets before sending it to customers. Explore device previews.

The current rendering catalogue includes Apple Mail on iPad, Apple Mail on iPhone, Apple Mail on macOS, Gmail on Android, Gmail on iPhone, Gmail web, Outlook on Android, Outlook on iPhone, Outlook web, Yahoo Mail web, classic Outlook on Windows, and new Outlook on Windows. Available appearances and targets vary, so select the exact client and device in the target picker. Android targets use emulators; iPhone and iPad targets use physical devices. The catalogue describes supported targets, while the application checks current availability. See rendering targets and profiles.

Yes. MailSlurp offers Outlook and Gmail rendering targets across the platforms listed in the target picker, including web and mobile variants and Outlook on Windows. Select the actual versions or platforms your recipients use. A good result in Gmail web does not establish that Outlook Windows or Gmail mobile will display the email identically. Compare email client screenshots.

Yes, for targets that offer a dark appearance. The current catalogue includes dark-mode targets for Gmail on Android, Gmail web, and Outlook on Android. Select a dark target explicitly and compare it with the corresponding light target. Do not assume every client supports the same appearance settings or makes the same changes to text, images and background colors. Choose light and dark targets.

Yes. Create a device preview test, select its targets and send the email to the test's special address from your email platform or connected sender. MailSlurp captures the delivered message on those targets. This lets you check the message your platform sends, including any changes it makes to the original HTML. Send an email for rendering.

Yes. Use the device preview API to create a test, supply or send the email as required by that workflow, check its status and retrieve the results. Wait for target results before downloading screenshots, and handle failed or unavailable targets separately. Screenshot access can require authentication or a time-limited URL. Automate device previews.

An inbox placement test sends a message to test mailboxes at different providers and reports where it lands, such as inbox or spam, or whether it has not yet been observed. MailSlurp lets you test a real sender and message before a wider send. These results describe the test mailboxes, not every future recipient. Explore inbox placement testing.

Create an inbox placement test and send the message from the sender you want to check to its seed addresses. Wait for the test to collect results, then compare inbox, spam and unobserved outcomes by provider. Use the same sending service and relevant message content as the email you intend to send. Run a placement test.

No. A spam score estimates risk using message or filtering rules. An inbox placement test observes where a delivered message lands in test mailboxes. A low score does not guarantee inbox delivery. Use placement results alongside sender authentication, reputation and message checks when investigating delivery problems. Understand placement results.

MailSlurp placement tests use the mailbox providers and seed addresses shown when you configure a test. Check that selection before sending; available seeds can change. Read the result for each provider rather than treating the overall percentage as a guarantee for all Gmail, Outlook, Yahoo or other recipients. Choose a test seed list.

Yes, when you can send the test email from that account or service to the supplied seed addresses. You can send from your own platform or use a supported connected sender. Keep the real sending route: sending the same HTML from a different server measures a different sender and delivery path. Test your sending service.

Yes. Use the API to create a test, obtain its seed addresses, send the email, check its status and read provider-level results. Allow time for collection and distinguish unobserved messages from confirmed spam placement. Compare repeated tests using consistent senders and relevant content, within your account's test limits. Automate placement testing.

Email warmup gradually introduces sending activity for a mailbox or sender instead of immediately starting at a large volume. MailSlurp provides warmup controls and monitoring for supported senders. Warmup works alongside correct SPF, DKIM and DMARC settings, wanted mail and sensible sending practices; it does not guarantee inbox delivery. Explore email warmup.

Connect a supported sender, configure the warmup settings and start the campaign when you are ready. MailSlurp manages the warmup activity according to those settings and exposes progress and results. Review the sender's limits and health as activity increases, and adjust the campaign to match your intended use. Configure a warmup campaign.

Yes. Connect a supported Gmail or Google Workspace sender, or use an authenticated SMTP connection. Microsoft 365 requires a compatible business mailbox with authenticated SMTP enabled. Check the provider setup before starting; mailbox policies and sending limits still apply. Use the current connection catalogue to confirm the requirements for other providers. Connect a warmup sender.

There is no single duration that guarantees a sender is ready. The appropriate ramp depends on mailbox and domain history, current sending volume, provider limits and the volume you intend to send. Monitor progress and delivery signals instead of treating a fixed number of days as proof of inbox placement. Review warmup progress.

Warmup manages gradual sending activity over time. Inbox placement testing measures where a particular test email lands in provider mailboxes. Use warmup monitoring to follow the campaign and placement tests to check actual delivery outcomes. Neither replaces sender authentication or permission to email the recipients on your list. Measure inbox placement.

An email parser extracts information from messages, such as order numbers, dates, addresses or amounts. MailSlurp supports email parsing and AI extraction so your application can turn incoming messages into structured data. Choose deterministic matching for fixed formats or AI extraction when wording and layout vary. Explore email data extraction.

Yes. Define the fields you want and an output schema supported by MailSlurp, then run extraction against the email content. The result can feed your application as structured JSON. Validate required fields and values before acting on them; structured output does not guarantee that every extracted fact is correct. Define an output schema.

Yes. MailSlurp provides attachment extraction and OCR workflows for supported documents and images. Fetch the attachment and use the appropriate extraction operation for its format. Attachment processing is a separate step from reading the email body, and supported formats and limits depend on the operation. See AI and extraction workflows.

Yes. Use an incoming-email webhook to notify your application, fetch the email and relevant attachments, then call the extraction API with your output schema. Validate the result before saving it or triggering another action. Handle duplicate webhook deliveries so the same message is not processed twice. Connect incoming email to your application.

Use regular expressions or fixed matching when the message format is predictable, such as a verification code with a known pattern. AI extraction is useful when equivalent information appears in different wording or layouts. For either approach, check the extracted values against the rules your application needs. Compare email extraction options.

Yes. Clients that support compatible remote MCP connections can use MailSlurp's hosted MCP server. Follow the setup for your client, connect your MailSlurp account and approve the permissions it needs. Available tools depend on those permissions and your account. Skills provide additional workflow instructions; client support and setup differ. Connect an AI client and find skills.

Yes. Create an account to see the available free access, trials and usage limits. Email and SMS operations, device rendering, placement testing, warmup and AI processing have different capacity and feature requirements. Check the current plan details and the price shown before confirming a paid action or renting a resource. Compare current plans.