Receive verification codes
Wait for an incoming SMS and read the code your test needs to complete a login or verification step.
A Twilio alternative for SMS and OTP testing.
Receive real text messages, retrieve verification codes and finish the login flow. MailSlurp connects phone numbers, SMS APIs and email testing.
Trusted by teams at
A real phone number for the workflow you need.
Choose an available number in MailSlurp and manage it in the dashboard or through the API. Receive SMS for application workflows, verification codes and automated testing.
Check the current country availability, number capabilities and plan before provisioning. Give test flows their own numbers so incoming messages are easy to match.
Explore phone numbers and SMS
Work in the dashboard or API
Inspect a message manually, then automate the same workflow when it needs to run repeatedly.
Connect incoming events
Use webhooks to notify your application when an SMS arrives.
Test the email and the text in the same journey.
Create an inbox and phone number for your test user. Complete the email signup, receive the SMS code and verify the final application state in your existing test runner.
Explore end-to-end testing
How to test an SMS flow
Choose a number
Select an available phone number and note its capabilities. Enter that number in the application flow you want to test.
Trigger and receive the text
Request the code or notification in your app. Use the dashboard, wait APIs or a webhook to retrieve the expected message.
Check the application outcome
Extract the code, complete the verification and assert the next screen. Repeat the workflow in CI using the SMS testing examples.
Put your SMS flow under test.
Create your free account, choose a phone-number plan and receive the messages your tests need.
Test what happens when the verification text arrives.
Use a MailSlurp number as the test recipient and record the time before requesting the SMS. Wait for a fresh message to that number, retrieve its code and submit it in the same browser session. Check that the expected account is signed in after verification.
Keep the number reserved until the test finishes. Run the same receipt and account checks in Playwright, Cypress, Selenium or your existing test runner.
Follow the Playwright SMS test
Check delivery before changing services.
Test receipt before migrating SMS services
For a Twilio Verify workflow, you can keep the service that sends the verification message and use MailSlurp to test its receipt and completion. For a broader SMS migration, map the number capabilities, outbound requirements and webhook handling before moving each workflow. The receive-SMS API guide covers bounded waits and webhooks.
Questions before you switch?
What should I verify in an SMS OTP test?
Reserve a MailSlurp number with the capabilities your test needs, then enter it in your app and record the time before requesting the code. Wait for the current message to that number, inspect the sender and retrieve the code. Submit it in the same session and check the expected account. Keep the number reserved until verification finishes. See the SMS testing workflow.
Can I test a Twilio Verify flow with MailSlurp?
Yes. Use a MailSlurp number as the test recipient, trigger the SMS from your application and retrieve the code to complete the verification. Check the current number capabilities and plan when selecting a number. Receive the current SMS code and complete verification.
Can I combine email and SMS tests?
Yes. Give the test user an inbox and a phone number, receive the messages and complete both steps in your existing test runner.
Test the text that completes the journey.
Create an account and choose the phone-number plan your workflow needs.