HTTP, SMTP, virtual, and expiring inbox types
Provision inboxes that match the job, from no-send capture and short-lived QA addresses to long-lived operational mailboxes.
Inbox infrastructure for developers
Provision real email addresses with API control
Create inboxes per user, workflow, or test run. Receive, parse, and assert messages without shared mailboxes or manual checks.
Trusted by teams shipping customer messaging
Built for production workflows
MailSlurp features for programmable email addresses
Create the inbox type you need, control it through API and SMTP/IMAP, and keep message handling tied to the workflow that owns it.
Custom domains, aliases, and catch-all addressing
Create branded inboxes and masked addresses on verified domains while keeping routing and ownership under API control.
Send, receive, search, and wait through one inbox surface
Use API, SMTP, and IMAP access together with wait functions, search endpoints, and latest-message helpers instead of stitching together separate tools.
Webhooks, rules, and extraction-ready message data
Attach webhooks, rulesets, and parsing helpers to each inbox so inbound mail can drive testing, automation, and downstream systems immediately.
Email address API
Key workflows
Signup, support, routing, and automation all get easier when addresses are created, tagged, and controlled through APIs instead of mailbox sprawl or manual setup.
Workflow 01
Create addresses on demand
Generate random, expiring, or custom-domain inboxes with tags and metadata for deterministic routing.
Workflow 02
Combine API automation with dashboard visibility
Let engineers automate mailbox lifecycles while QA and support inspect message state in shared workspaces.
Workflow 03
Wait, parse, and assert inbound messages
Use wait-for APIs and extraction helpers to verify links, OTP codes, attachments, and headers in CI.
Developer integration
Use inbox APIs, SMTP, and webhook events in the same workflow
Start with SDK helpers for inbox creation and message waits, then move into event-driven routing when the workflow expands.
- Generated SDKs for major languages
- API + SMTP + IMAP support where needed
- Docs-backed patterns for inboxes and message assertions
Next step
Start with signup or docs
Use the free account to validate the workflow in your own stack, then move into implementation details in the docs.