Test OTP verification across SMS, email fallback, MFA, and recovery

MailSlurp gives QA and engineering teams real phone numbers, receive-SMS APIs, deterministic OTP capture, retry evidence, and email fallback coverage for signup, login, recovery, and MFA flows.

Start free Talk to sales

SMS verification API for OTP and 2FA workflows

Trusted by top companies worldwide

Programmable SMS numbers for verification workflows

Provision real numbers for SMS verification tests

Create a dedicated number for each environment, country, or test run. Trigger the same signup, login, MFA enrollment, or account recovery flow customers use, then keep the phone identity and received message attached to the test result.

MailSlurp (examples)

const sms = await mailslurp.waitController.waitForLatestSms({
  waitForSingleSmsOptions: {
    phoneNumberId: phone.id,
    timeout: 30_000,
    unreadOnly: true,
  },
});
expect(sms.body).toContain('Here is your code');
expect(sms.fromNumber).toEqual('+13252527014');

Receive the OTP, parse the code, and assert the verified state

Wait for the inbound SMS, extract the one-time code, submit it through the browser or API flow, and fail clearly when delivery is late, the template changes, or retry controls allow the wrong code.

MailSlurp (examples)

const sms = await mailslurp.waitController.waitForLatestSms({
  waitForSingleSmsOptions: {
    phoneNumberId: phone.id,
    timeout: 30_000,
    unreadOnly: true,
  },
});
expect(sms.body).toContain('Here is your code');
expect(sms.fromNumber).toEqual('+13252527014');

SMS and OTP verification API workflows MailSlurp supports

Turn phone number and OTP verification into a repeatable API flow: provision a number, trigger a challenge, receive the SMS, parse the OTP, submit it, and capture the final auth outcome.