Every testing scenario your Team Actually Runs Into
Real workflows, concrete setups, and specific configurations — for backend developers, QA engineers, and DevOps teams testing email, SMS, webhooks, and TOTP in staging.
SMS
Webhook
MFA/TOTP
CORE USE CASES
Start here — the scenarios every team tests
The most common testing workflows. If you're new to Sandbox or migrating from another tool, these four cover the flows your app relies on most.
Transactional Email Testing
Replace your SMTP provider with a mock SMTP server in staging. Every email your app sends — welcome, password reset, order confirmation — lands in Sandbox instead of a real inbox. Inspect HTML rendering, score deliverability, and validate every detail before a single real user sees it.
SMS OTP Testing
Test your SMS OTP flow end-to-end — request, delivery, expiry, retry — without a real carrier, real credits, or real recipients. Validate Sender ID, message body, and DLT template rendering in a mock SMS gateway before a single real number is contacted.
Webhook Testing
Point your services at an authenticated webhook endpoint instead of a real destination. Every payload — Stripe, GitHub, Discord, or your own — lands in a permanent team inbox. Inspect headers, body, and validation status. No more "did the webhook fire" in Slack.
OTP and 2FA Testing
Test your entire 2FA login flow — enrollment, code generation, validation, expiry, and retry — without a real authenticator app or real user credentials. QA signs off on the flow before any real user goes through it. Covers both TOTP and email OTP flows.
BY PRODUCT AND INDUSTRY
Scenario-Specific Guides
More detailed guides for specific product types, industries, and integration patterns — covering the exact setup your team needs.
Email testing for SaaS
Onboarding sequences, trial expiry nudges, and feature announcement emails — tested before your next deploy touches a real user.
Email testing for Ecommerce
Order confirmations, shipping alerts, and cart recovery emails — validated for HTML rendering and link integrity before your next release.
OTP testing for Fintech
High-stakes OTP flows for payments, fund transfers, and account access — tested against strict expiry windows and retry limits before production.
Webhook testing for Payment Gateways
High-stakes webhook flows for payments, fund transfers, and account access — tested against strict expiry windows and retry limits before production.
Still don't see your use case?
Tell us what you're building and what you want to simulate in Sandbox. Our team will create a step-by-step guide, share sample code, and recommend the best setup tailored to your stack and workflow.
Custom testing guides for your product flows
Integration setup help and example payloads
Automation tips for CI/CD and staging environments
Best practices for email, SMS, webhook, and TOTP testing
FAQ'S
Common Questions About Testing With Sandbox
Do I need real phone numbers, email accounts, or bank credentials to test these flows?
No. Every scenario runs entirely inside Sandbox — a mock SMTP server, a mock SMS gateway, a real authenticated webhook endpoint, and a TOTP inbox. No real recipients, carriers, or user credentials are ever involved.
Do I need a separate Sandbox account for each testing flow?
No. One Sandbox workspace covers email, SMS, webhooks, and TOTP — your whole team works from the same account and sees the same test data.
Is there a limit to how many test emails, SMS, webhooks, or OTPs I can send?
Limits are based on your plan. All plans include a generous free tier suitable for staging and QA workflows.
Can I run these tests inside CI/CD pipelines?
Yes. Every inbox and endpoint in Sandbox is reachable via API, so you can wire email, SMS, webhook, and OTP checks directly into your pipeline instead of running them manually before each release.
What if my exact use case isn't listed on this page?
Request it. Tell us what you're building and what you want to simulate, and our team will put together a step-by-step guide and sample code for your specific stack.
Can multiple team members see the same test data at the same time?
Yes. Every inbox is shared across your team by default — no per-seat setup needed to give a teammate visibility into the same test flow.
THE ZUNOY SANDBOX SUITE
Every Testing Scenario, One Sandbox Workspace
Your app sends emails, SMS, webhooks, and TOTP codes. Sandbox handles all four — in one workspace, under one account, visible to your whole team.
Email Inbox
SMS Inbox
Webhook Inbox
TOTP Inbox