Web UI
- Review inbox messages with subject, sender, and timestamps.
- Open plain text and HTML content for manual QA verification.
- Manage account settings and API keys from one place.
Built for QA and development teams
Test outbound emails before your users do
Create a persistent testing inbox for |
Create a free account to generate your persistent inbox address.
Already have an account? Sign in
MCP endpoint
https://mcp.devmail.space/mcp Two products for one email testing workflow
DevMail is delivered as a visual Web UI and an API for programmatic checks.
API
- Pull messages in CI pipelines and automated test suites.
- Query inbox state and message data programmatically.
- Use API to verify count of received messages.
Feature highlights
Keep the same email flow from local debugging to automated verification in CI without changing tools.
Persistent inbox address
Use one generated mailbox per user for repeatable test scenarios.
Faster, more stable email testing
Receive test emails quickly and verify them predictably through the DevMail API.
HTML and text inspection
Validate templates, variables, links, and rendered email content quickly.
Attachment Download Support
Access PDF and image attachments with secure, reliable download functionality.
Team Access
Shared inbox mean no more manual forwarding of test emails.
Reliable test workflows
Run repeatable email checks in CI and staging to confirm emails arrive and contain the expected data before release.
Inbox aliases
Route inbox+tag@domain to one inbox for scenario-based testing.
How It Works
- 1 Create your account
Register once and receive a unique persistent testing inbox.
- 2 Send test traffic
Point signup, notification flows to your generated inbox address. You can segment tests with plus-address aliases.
- 3 Review in Web UI
Inspect message content manually to catch template and logic issues.
- 4 Get API key
Generate API key in your account settings.
- 5 Automate with API
Assert message delivery and content from CI via API endpoints.
- 6 Avoid maintenance
Inbox messages are automatically cleaned up.
Common use cases
Designed for practical client workflows across engineering and QA teams.
Release readiness checks
Confirm key transactional emails are delivered and readable before deployment.
CI quality gates
Block merges when expected emails are missing, malformed, or delayed.
Manual exploratory QA
Spot visual or content regressions in onboarding, reset, and notification journeys.
Shared staging environments
When partners or clients use staging, route only automation-critical flows to a dedicated DevMail inbox for reliable regression checks.
Scheduled smoke checks
Verify recurring emails from external services without inbox buildup. Use DevMail for periodic checks while old messages clear automatically.
Indie hackers testing signup and login emails
Verify signup, password reset, invite, and magic-link flows quickly in one persistent inbox without extra setup overhead.
Important use notice
- This service is for development and testing workflows only.
- Do not use DevMail for personal, sensitive, or production user communications.
- Received email data can be removed according to retention and platform policy.
- Read terms and privacy policy before using the service in your team workflow.
See Terms and Conditions and Privacy Policy.
Start validating email flows with your team
Create an account for UI checks, then generate API keys for automation.