SMS API
MailSlurp gives teams real phone numbers for verification, OTP, inbound processing, and release-grade testing across regions.
Trusted by teams shipping customer messaging
Product features
Use the MailSlurp features that make the workflow work reliably in production, not just in a quick demo.
Create numbers according to region and plan availability instead of sharing one handset or relying on mock SMS endpoints.
MailSlurp gives teams deterministic receive primitives for inbound SMS instead of manual handset checks or mailbox-style polling.
Manage emergency-address, consent, and other sending prerequisites on the number itself before production traffic depends on it.
Inspect sent and received message history for each number, pull OTP codes from real payloads, and keep durable records when a flow fails.
Key workflows
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 account verification flows with real numbers, deterministic waits, and message extraction in code.
Workflow 02
Use SMS when the product needs a second verification channel or a recovery path that cannot depend on email alone.
Workflow 03
Capture and process inbound messages through APIs and webhooks instead of unmanaged inboxes or manual review.
Developer integration
Provision numbers, receive SMS, and validate mobile verification flows with SDKs, webhooks, and deterministic wait helpers.
Use real numbers
Start with one critical mobile flow with real numbers and deterministic waits, then expand into broader SMS operations once the base path is trusted.
