9:41

MailSlurp

iMessageToday 9:32 AM

Your MailSlurp verification code is 482913.

Code received.

iMessage

Catch SMS signup bugs before your users do

Give your tests real phone numbers. MailSlurp receives the SMS and lets your code read the OTP, so you can test signup, login and recovery without reaching for a handset.

Run your first OTP test Talk to sales

9:41

MailSlurp

iMessageToday 9:32 AM

Your MailSlurp verification code is 482913.

Code received.

iMessage

Trusted by top companies worldwide

SMS dashboard

See the message your test received

Open the dashboard to inspect a phone number, read its received messages and follow its message events. When a test fails, you can look at the actual SMS instead of guessing what arrived.

9:41

MailSlurp

iMessageToday 9:32 AM

iMessage

Assign a number to each SMS test

Give each running test its own assigned number or lease one from a phone pool. That keeps parallel tests from picking up each other's codes, so you can check the right signup or login.

import { MailSlurp } from 'mailslurp-client';

const apiKey = process.env.MAILSLURP_API_KEY;
const phoneNumberId = process.env.MAILSLURP_PHONE_NUMBER_ID;
if (!apiKey || !phoneNumberId) {
  throw new Error('Set an API key and the ID of your assigned test number');
}
const mailslurp = new MailSlurp({ apiKey });
const phoneNumber = await mailslurp.phoneController.getPhoneNumber({ phoneNumberId });
// Give phoneNumber.phoneNumber to your app. Use phoneNumber.id in API calls.

9:41

MailSlurp

iMessageToday 9:32 AM

iMessage

MailSlurp (examples)

import { MailSlurp } from 'mailslurp-client';

export async function checkSmsLogin(
  mailslurp: MailSlurp,
  phoneNumber: { id: string; phoneNumber: string },
  actions: {
    requestCode: (number: string) => Promise<void>;
    submitCode: (code: string) => Promise<void>;
    assertSignedIn: () => Promise<void>;
  },
) {
  // Reserve this number exclusively for this attempt before calling the helper.
  const since = new Date();
  await actions.requestCode(phoneNumber.phoneNumber);
  const sms = await mailslurp.waitController.waitForLatestSms({
    waitForSingleSmsOptions: {
      phoneNumberId: phoneNumber.id,
      since,
      timeout: 60_000,
      unreadOnly: false,
    },
  });
  // Adapt this exact template to the SMS your application sends.
  const match = /^Your code: ([0-9]{6})$/.exec(sms.body ?? '');
  if (!match) throw new Error('SMS did not match the expected OTP template');
  await actions.submitCode(match[1]);
  await actions.assertSignedIn();
}

Take the code all the way to a successful login

Wait for the SMS, extract the code and enter it in your app. Check that verification succeeds, then test what happens when the code arrives late, expires or gets entered twice.

MailSlurp (examples)

import { MailSlurp } from 'mailslurp-client';

export async function checkSmsLogin(
  mailslurp: MailSlurp,
  phoneNumber: { id: string; phoneNumber: string },
  actions: {
    requestCode: (number: string) => Promise<void>;
    submitCode: (code: string) => Promise<void>;
    assertSignedIn: () => Promise<void>;
  },
) {
  // Reserve this number exclusively for this attempt before calling the helper.
  const since = new Date();
  await actions.requestCode(phoneNumber.phoneNumber);
  const sms = await mailslurp.waitController.waitForLatestSms({
    waitForSingleSmsOptions: {
      phoneNumberId: phoneNumber.id,
      since,
      timeout: 60_000,
      unreadOnly: false,
    },
  });
  // Adapt this exact template to the SMS your application sends.
  const match = /^Your code: ([0-9]{6})$/.exec(sms.body ?? '');
  if (!match) throw new Error('SMS did not match the expected OTP template');
  await actions.submitCode(match[1]);
  await actions.assertSignedIn();
}

Release gate

Find out where the SMS test got stuck

Record the step that failed, its message IDs and how long it took. You'll have something useful to investigate without putting private codes or message bodies in shared CI logs.

Debug email and SMS tests

Phone checks are running

0 of 4 phone checks complete

Hide all checks

mailslurp: allocate phone number-Fresh test number reserved for this run

RequiredDetails

playwright: submit phone verification-Signup flow requested an SMS challenge

RequiredDetails

mailslurp: wait for sms otp-Latest inbound SMS captured from the real network

RequiredDetails

qa: extract verification code-One-time code parsed and submitted

RequiredDetails

Waiting for SMS verification checks

CI will unblock once the real SMS challenge completes.

Put your signup, login and recovery flows to the test

A received code is only part of the job. Follow it through your application and check that the person signing up, logging in or recovering an account can finish.

Test email and SMS together

Check SMS codes, fallback emails, magic links and MFA in the same test suite.

Open OTP testing guide

Get numbers for your tests

Use programmable numbers for QA, staging and regional checks without keeping a drawer full of test SIMs.

Open phone number SMS service

Test verification challenges

Check signup, login, MFA and recovery, including attempt limits and the wait between retries.

Open phone verification API

Receive and parse OTP codes

Read the delivered message, extract its code and check that your app accepts it for the right account.

Open SMS API guide

Cover authentication flows

Extend your tests to MFA setup, account recovery, payment confirmation and fallback emails.

Open OTP testing solution

Automate SMS OTP in Playwright

Let Playwright request a code, read it through MailSlurp and enter it in the browser, just as your user would.

Open Playwright OTP guide

Integrate MailSlurp Seamlessly

Integrate with any framework

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

CI/CD Native

MailSlurp fits right into your existing development, testing, and CI/CD workflows. Deploy and iterate with confidence and actionable feedback.

Developer Integrations

SMS OTP testing workflows at global scale

Mobile networks

20+

Use real network behavior for verification checks.

Verification coverage

OTP + MFA

Cover signup, login, account recovery, and MFA journeys.

Developer APIs

SDKs

Create numbers, wait for SMS, and extract OTPs from code.

Build with MailSlurp

Connect & learn

Catch SMS signup bugs before your users do

See the message your test received

Assign a number to each SMS test

Take the code all the way to a successful login

Phone checks are running

Waiting for SMS verification checks

Put your signup, login and recovery flows to the test

Test email and SMS together

Get numbers for your tests

Test verification challenges

Receive and parse OTP codes

Cover authentication flows

Automate SMS OTP in Playwright

Integrate with any framework

CI/CD Native

SMS OTP testing workflows at global scale

The complete email and SMS toolkit.