The email and SMS testing and development platform

MailSlurp gives engineering and QA teams programmable inboxes, real phone numbers, deterministic waits, webhooks, and payload inspection for email and SMS workflows.

Start free Talk to sales

Trusted by top companies worldwide

Programmable inboxes and phone numbers in MailSlurp

Create isolated message identities on demand

Generate disposable or permanent inboxes and phone numbers per test run, user journey, environment, or customer workflow so messages never collide across teams or parallel CI workers.

Use aliases, custom domains, Gmail and Outlook connections, inbound routing, and real mobile networks from one MailSlurp account.

Explore product features

Automate real email and SMS assertions from test code

Use the MailSlurp API and SDKs to create inboxes and phone numbers, receive messages, extract OTP codes, assert links and content, and gate releases in CI.

Start testing View SDKs

MailSlurp testing examples

import { test, expect } from "@playwright/test";
import { MailSlurp } from "mailslurp-client";

test("signs up with a real confirmation email", async ({ page }) => {
  const mailslurp = new MailSlurp({
    apiKey: process.env.MAILSLURP_API_KEY!,
  });
  const inbox = await mailslurp.createInbox();

  await page.goto("https://playground.mailslurp.com");
  await page.getByText("Create account").click();
  await page.getByLabel("Email").fill(inbox.emailAddress!);
  await page.getByLabel("Password").fill("Password123!");
  await page.getByRole("button", { name: "Create" }).click();

  const email = await mailslurp.waitForLatestEmail(inbox.id!, 60_000, true);
  const code = /\b[0-9]{6}\b/.exec(email.body ?? "")?.[0];
  expect(code).toBeTruthy();

  await page.getByLabel("Confirmation Code").fill(code!);
  await page.getByRole("button", { name: "Confirm" }).click();
  await expect(page.getByText("Account confirmed")).toBeVisible();
});

SDKs for automated testing frameworks

Test email and SMS without changing your stack.

Bring MailSlurp into the frameworks and CI pipeline you already use, then inspect every message, assertion, and failure in one visual dashboard.

Use any test framework

Playwright

Cypress

Selenium

WebdriverIO

pytest

JUnit

Add real email and SMS to Playwright, Cypress, Selenium, WebdriverIO, pytest, JUnit, and the tools already in your test suite.

Explore integrations

Run every flow in CI

All message checks passed

3 successful CI checks

Create test inbox-ready

RequiredDetails

Verify email journey-passed

RequiredDetails

Capture SMS code-passed

RequiredDetails

Create isolated inboxes and phone numbers per build, run tests in parallel, and block the merge when a real message journey fails.

Explore CI testing

See every result in one dashboard

Visual dashboard showing an SMS flow, message preview, assertions, and CI release proof

Inspect received email and SMS, OTPs, assertions, timings, and failures visually instead of piecing the story together from CI logs.

Explore visual testing

Build reliable email and SMS workflows

Use MailSlurp across the places where teams need real messages, repeatable assertions, and evidence they can debug.

Inbox API

Create inboxes in code, receive messages, search content, inspect headers, download attachments, and assert payloads without shared mailbox state.

Explore inbox APIs

Email and SMS testing

Cover OTP, MFA, magic links, password resets, account invites, billing notices, alerts, and product notifications with real inboxes and phone numbers.

Open QA testing

Inbound webhooks

Stream inbound email and SMS events to applications, queues, support tools, and review workflows with retries and observable delivery.

View webhooks

Device previews

Preview delivered emails across supported mailbox clients and device contexts before templates, campaigns, or transactional messages reach customers.

Email previews across supported clients and devices

Open device previews

Delivery checks

Pair release testing with inbox placement, spam checks, sender authentication, and domain monitoring when delivery quality matters.

Inbox placement and deliverability checks

Explore deliverability

Developer checks are running

0 of 4 CI checks complete

Hide all checks

sdk: generate isolated inbox-Fresh MailSlurp inbox created for this CI run

RequiredDetails

playwright: complete signup-Browser flow submitted the generated email address

RequiredDetails

mailslurp: wait for auth email-Verification email received and parsed from a real inbox

RequiredDetails

release: publish evidence-Message IDs and assertions attached to the build

RequiredDetails

Waiting for MailSlurp checks

CI will unblock once the real message assertion completes.

Gate releases on real message evidence

Attach inbox creation, browser completion, message receipt, and assertion status to CI so teams can merge only when critical email and SMS workflows pass.

View testing platform

Use the same API in tests, dashboards, and CI

Control MailSlurp from REST APIs, native SDKs, SMTP, IMAP, webhooks, and shared dashboards so developers, QA, and platform teams can use the same inbox and phone-number primitives.

Open developer integrations

Message testing infrastructure at production scale

Emails processed

500 million+

Scale for CI, staging, automations, and production workflows.

Mobile networks

20+

Use real phone numbers for SMS, OTP, and MFA test coverage.

Mature platform

10+ years

Stable APIs for long-running engineering and QA teams.

Start with one inbox, then expand across every message workflow

Create a free MailSlurp account, validate a signup or reset email today, then add SMS, webhooks, device previews, and delivery checks as your coverage grows.

Create free account View docs