MailSlurp helps teams build and validate email workflows end-to-end: inbox provisioning, inbound processing, outbound testing, deliverability diagnostics, and operational controls around retention and review.
Use this hub when you need to choose the right email API surface, route inbound messages into business systems, tighten sender trust, or compare disposable and temporary inbox options before you commit to an implementation path.
API foundations
Start here if you are designing email infrastructure, provisioning addresses for an application, or deciding how MailSlurp fits into your outbound and receive stack.
- Email API overview for the broad capability map across inbox provisioning, send, receive, and automation.
- Email API for developers for the product-level view of how MailSlurp fits into production systems.
- Email address API when you need programmable addresses, aliases, and inbox ownership.
- Send email API for application-triggered sending, release controls, and integration planning.
- SMTP API if your team is comparing API-first send models with SMTP relay and existing SMTP submission workflows.
- Receive email API for deterministic retrieval, assertion-friendly polling, and message access patterns.
- Google email API if you are comparing Gmail or Workspace mailbox automation with controlled inboxes for testing and receive-side proof.
Inbound workflows
Choose this section when the email itself is the trigger for work: support intake, invoice processing, order mailboxes, routing rules, or structured data extraction.
- Inbound email API for webhook delivery, parsing, routing, and attachment-aware workflows.
- Receive email API when you need deterministic polling or test-friendly fallback retrieval.
- Email webhooks for implementation patterns around near-real-time event delivery.
- Email automation and routing for policy-driven forwarding, retries, and controlled workflow design.
- Inbound email routing for the business workflow view of support, finance, and operations use cases.
- AI email parsing and structured extraction when inbound messages need to become typed data, not just raw mailbox content.
Deliverability and trust
Use these pages when sender authentication, routing visibility, and release confidence matter more than generic mailbox access.
- DNS lookup when you need a fast read on SPF, DKIM, DMARC, MX, or routing records.
- SPF checker, DKIM checker, and DMARC checker for sender-policy validation before or after change windows.
- Email header analyzer to inspect real-message auth and path results when delivery looks wrong.
- Inbox placement test for release checks that go beyond record validation.
- DMARC, SPF, and DKIM monitoring for recurring checks, alerting, and run history around sender posture.
- DMARC monitoring if you need a guide to operationalize sender-domain visibility.
Governance and compliance
Use this lane when email records need retention rules, reviewability, or evidence that message handling is controlled and auditable.
- Email archiving software for preserving communications in a way that supports retrieval and downstream review.
- Email retention policy for designing schedules, ownership, and deletion boundaries.
- HIPAA email workflow guide when protected health information affects how messages are stored and handled.
- SOC 2 communications controls for controls language that maps email workflows to governance requirements.
Temporary and disposable evaluation
This lane is useful when you are comparing inbox models, testing privacy boundaries, or deciding whether a disposable, temporary, or sandboxed environment is the best fit for the job.
- Free email API capability overview for a practical starting point when you are comparing options and constraints.
- Disposable email API for private inboxes in CI, QA, signup testing, and automation.
- Temporary email API for time-boxed workflows where address lifetime and retention boundaries matter.
- Email Sandbox API for isolated testing environments that should not touch production traffic.
- Fake email generator for fast manual evaluation before you move to private API-managed inboxes.
Where to go next
- Need a general starting point? Begin with Email API overview.
- Need a workflow page for stakeholders outside engineering? Use Inbound email routing.
- Need a testing-first path? Continue to Email integration testing and Test email accounts.