Integrate with any framework
Official plugins and SDKs for all major programming languages, frameworks, and test platforms. All functionality available via API or dashboard.

MailSlurp gives QA and engineering teams programmable inboxes and phone numbers for integration tests. Create test identities, wait for email or SMS, extract codes and links, assert message content, and keep CI release gates deterministic.
Trusted by top companies worldwide




Create disposable email addresses and programmable phone numbers on demand, then control email and SMS from Playwright, Cypress, Selenium, Jest, or your own integration test harness.
Use bounded waits, sender and subject matching, regex extraction, attachment inspection, webhook events, and SDK helpers so email and SMS tests fail with useful evidence instead of timing noise.
Integrate MailSlurp Seamlessly
Official plugins and SDKs for all major programming languages, frameworks, and test platforms. All functionality available via API or dashboard.

MailSlurp fits right into your existing development, testing, and CI/CD workflows. Deploy and iterate with confidence and actionable feedback.
Open a delivered message and run the audit from the inbox. Review the health score, work through broken assets, personalization, accessibility, HTML support and sender findings, then send another test to confirm the fixes.

After CI proves the signup, OTP, reset, or notification flow completes, use MailSlurp device previews and email audit checks to review the delivered message, verify links, and keep evidence for the next release.
Cover the customer journeys that usually break quietly: authentication, onboarding, payments, alerts, and inbound automation.
Receive SMS and email codes in code, extract the OTP, and complete the same verification flow customers use.
Create a real inbox, trigger signup or invite email, extract the link, and continue the browser journey.
Assert reset sender, subject, link, token, and timing before authentication changes reach production.
Inspect MIME parts, headers, files, recipients, links, and message metadata from API responses.
Create inboxes and numbers per worker so tests do not collide across parallel builds or shared staging data.
Preview important delivered emails and audit links or assets after the core browser or API journey passes.
Keep browser tests independent while checking the same signup, OTP, reset, and notification messages customers rely on.
Create a MailSlurp inbox for the Cypress test, submit its address through your signup or login flow, then wait for the matching message through the MailSlurp API. Extract the OTP with a pattern, enter it in the browser, and keep the received email with the test result when a failure needs investigation. Read the Cypress email testing guide.
Provision a fresh MailSlurp inbox in the Playwright test or worker fixture and use that address during signup. The test can wait for the real delivered email, open its verification link, and finish the browser journey without shared credentials, inbox cleanup, or messages left by another run. Read the Playwright email testing guide.
Call the MailSlurp inbox API during test setup and store the new inbox ID and email address with that run. Create one inbox per worker or scenario, apply an expiry when appropriate, and wait by inbox ID so parallel builds never read one another's messages. Read the inbox creation guide.
Messages processed
500 million+
Scale for CI, staging, and production checks.
Channels covered
Email + SMS
One platform for inboxes, phone numbers, OTP, and webhooks.
Mature platform
10+ years
Stable APIs for long-running test suites.