MailSlurp Documentation
Build, test, monitor, and automate real email and SMS workflows
Start with the platform pillar you actually need. Messaging, testing, monitoring, automation, governance, and developer APIs each have a clear entry point.
Core platform pillars
MailSlurp is easiest to understand as six product pillars. Start at the one closest to your job-to-be-done, then branch outward only if needed.
Core messaging
Messaging
Provision inboxes, domains, phone numbers, and connected mailboxes for production and testing workflows.
Release confidence
Testing and QA
Validate async communication paths with message waits, compatibility checks, rendering previews, and release gates.
Production health
Monitoring
Track sender health, DNS drift, and live campaign output after release instead of relying on manual spot checks.
Event-driven workflows
Automation
Handle inbound traffic, trigger downstream systems, and turn messages into structured workflows.
Shared access control
Team and governance
Keep access, environments, and sign-in controls boring before your production footprint grows.
Implementation layer
Developer APIs
Use SDKs, API reference, examples, and protocol access patterns that fit your stack and delivery workflow.
Developer entry points
Common integrations, language SDKs, and API docs for developers building directly on MailSlurp.
Integrations
Common plugins, runners, and API clients for teams wiring MailSlurp into delivery workflows.
SDKs
Jump straight into the language client or package index that fits your application stack.
APIs
Reference and implementation guides for direct API usage, auth, examples, and protocol access.
Operational highlights
Focused tooling for sender health, campaign validation, and release confidence.
Campaign Probe
Watch live campaign output through controlled capture addresses and automated checks.
Device previews
Review rendering in the clients and devices your stakeholders actually care about.
Domain Monitor
Track sender-health posture and DNS drift before it becomes a delivery incident.