Create masked alias addresses with hidden destinations
Publish an alias email address without exposing the real inbox or system endpoint behind it.
Issue alias addresses and route inbound mail with API control
Create masked addresses, verify destinations, forward inbound messages, and keep reply behavior aligned with the workflow behind the alias.
Trusted by top companies worldwide
Alias controls
MailSlurp features for masked addresses and controlled forwarding
Create public-facing addresses that stay stable while the hidden destination, forwarding path, and reply behavior remain under API control.
Explore
Verify and rotate forwarding targets safely
Confirm destination ownership before activation and change the hidden target later without changing the public address.
Control forwarding and reply threading behavior
Keep forwarded mail and replies attached to the right workflow instead of letting mailbox-side forwarding break the conversation path.
Manage alias lifecycle through API and dashboard
Create, disable, rotate, and review aliases programmatically or through shared operational tooling when ownership changes.
Create masked alias addresses with hidden destinations
Publish an alias email address without exposing the real inbox or system endpoint behind it.
Verify and rotate forwarding targets safely
Confirm destination ownership before activation and change the hidden target later without changing the public address.
Control forwarding and reply threading behavior
Keep forwarded mail and replies attached to the right workflow instead of letting mailbox-side forwarding break the conversation path.
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.