Skip to main content

Quick start

MailSlurp gives your team real inboxes, phone numbers, testing tools, monitoring workflows, and automation primitives in one platform. The fastest way to get an "aha" moment is to create a fresh inbox, run one real message flow, and then branch into the workflow that matches your job.

Choose your starting point​

Developers

Create inboxes, domains, and numbers in code so product workflows stop depending on shared mailboxes.

Open

QA and release

Test sign-up, OTP, notifications, and message quality using deterministic waits and delivery checks.

Open

Marketers

Preview campaigns, audit email quality, and monitor sender or campaign health before and after launch.

Open

Data and ops

Capture inbound messages, extract structured content, and route events into downstream systems.

Open

1. Create an account and API key​

Before you run any workflow:

  1. Create a MailSlurp account.
  2. Generate an API key in developer settings.
  3. Decide whether you want to start with an SDK or direct REST calls.
Create account

2. Run your first real workflow​

Create a fresh inbox for a test, app flow, or operational automation. This is the core MailSlurp pattern: isolate the address, run the workflow, then inspect or wait for the resulting message.

SDK examples

MailSlurp supports JavaScript, Java, C#, PHP, Python, Ruby, and Go SDKs. The same workflows are also available over REST.

Loading...

Once you have an inbox, your next move is usually one of these:

3. Pick the platform track you actually need​

Messaging

Core inboxes, email, SMS, custom domains, attachments, and external mailbox connectors.

Browse messaging

Testing

End-to-end release confidence with waits, device previews, email audit, compatibility checks, and deliverability tests.

Open testing guide

Monitoring

Monitor domains, live campaigns, and sender health so issues are visible before customers notice them.

Open monitoring

Automation

Use webhooks, forwarding, routing rules, alias proxy, and AI transformers to turn messages into events and data pipelines.

Open automation

Governance

Share access safely with organizations, custom roles, environment isolation, SAML SSO, and storage controls.

Open governance

4. Best next docs by team​

5. Production readiness checklist​

  • Use environment-specific API keys instead of one shared key across every workflow.
  • Give production sender domains their own validation and monitoring path.
  • Create roles or per-user permissions before expanding team access.
  • Use deliverability checks and campaign monitoring before large sends.
  • Keep testing inboxes and production inboxes separated by environment or organization policy.