Email testing API

Email testing API for CI, signup flows, and notification checks

MailSlurp gives teams a programmable way to create inboxes, wait for matching messages, and validate email content in code. Use it to harden signup, reset, invitation, and notification flows before release.

Start free Open API docs

Trusted by teams shipping customer messaging

Product features

Capabilities that make the page valuable in practice

Use the MailSlurp features that make the workflow work reliably in production, not just in a quick demo.

Disposable and expiring inboxes you can create on demand

A testing API is only useful if inbox lifecycle is under your control, not tied to shared accounts or manual setup.

Create one inbox per suite, worker, or run
Use expiry and metadata to keep test assets organized
Support realistic email flows with clean isolation

Wait APIs that match the exact message you need

The difference between a toy inbox API and a release-worthy one is how reliably it waits and matches on real message state.

Wait for latest, first, or matching email
Match by sender, subject, unread state, or content
Replace brittle sleep calls with bounded waits

Parse links, codes, headers, and attachments directly

Pull the message data your workflow actually depends on instead of scraping inbox UIs or hand-rolling MIME parsing in every test suite.

Extract magic links, OTP codes, and body content
Inspect headers, recipients, and attachments
Assert the exact payload customers would receive

Artifacts and identifiers that support release gates

A strong setup turns one high-risk email workflow into a dependable release check the whole team can trust.

Keep inbox IDs and message IDs for failed runs
Give engineering and QA the same saved message records
Promote email checks into dependable release gates

Key workflows

High-value workflows for an email testing API

Start with the workflow you need most, then expand the same MailSlurp setup into adjacent use cases once the first route is working.

Workflow 01

Validate signup and invitation emails

Create an inbox, trigger your app flow, wait for the message, and assert that the link and content are correct.

See integration testing

MailSlurp product workspace showing email, phone, dashboard activity, and developer automation

Workflow 02

Assert password reset and recovery behavior

Verify the correct subject, sender, reset link, and timing before auth-related changes go live.

See auth testing

Workflow 03

Gate transactional and operational notifications

Use the same inbox automation for receipts, alerts, onboarding, and product-event notifications.

Open email platform

Developer integration

Drop message assertions into Playwright, Cypress, Selenium, or CI

Use SDK helpers inside your existing test runners instead of building mailbox polling and parsing from scratch.

iOS

Wait for matching email or SMS in test code
Extract links, codes, and headers for assertions
Run the same patterns locally and in CI

Open docs

Make email assertions real

Turn email checks into reliable release coverage instead of a manual chore

Start with one critical message flow with a programmable inbox and deterministic waits, then expand into broader integration testing once the team relies on it.

Start free View docs