Email Sandbox Alerts in Webhook for Every Sandbox Event
Connect Sandbox to your own systems. With email sandbox alerts in Webhook, every email received, SMS logged, or webhook captured fires an outbound HTTP POST to your endpoint — with a structured JSON payload your tools can act on immediately.
Works with any HTTP endpoint
Structured JSON Payloads
Active Immediately After Setup
What can you build with a custom webhook?
Anything that should react to a test event without a person watching. A CI test can wait for the sms.received event and read the OTP straight from the payload instead of polling an inbox, and every request is signed so your endpoint can check it really came from Sandbox.
Key takeaways
Three event types: email.received, sms.received and webhook.received. Each payload includes the inbox or project, sender or source, and a UTC timestamp.
Requests carry a signature header you verify with your webhook secret. If your endpoint is down, Sandbox retries with backoff for a limited time.
Connect several endpoints, each limited to its own inboxes and projects. Send a test payload before you save.
Common uses: CI/CD OTP checks, internal dashboards that track staging email, and syncing inbox events to a data warehouse.
Pause it any time from Integrations. Events still land in your inbox, they just are not sent on until you resume.
WHY USE A CUSTOM WEBHOOK
Not every team works in Slack or Discord. Your tools are your tools.
Custom webhook integration gives teams email sandbox alerts in Webhook while routing Sandbox events into their own systems — internal dashboards, monitoring tools, custom alerting pipelines, or any HTTP endpoint that can receive a POST request.
Payload structure is subject to change. Always refer to the latest Sandbox docs for the current schema.
POST REQUEST TO YOUR ENDPOINT WITH THIS STRUCTURE:
{ "event": "email.received", "inbox": "staging-qa", "from": "app@yourapp.com", "subject": "Welcome to YourApp", "received_at": "2026-04-24T10:32:00Z" }
SMS EVENT:
{ "event": "sms.received", "inbox": "sms-qa-inbox", "from": "YOBANK", "message": "Your OTP is 483920. Valid for 10 minutes.", "received_at": "2026-04-24T10:33:00Z" }
WEBHOOK EVENT:
{ "event": "webhook.received", "project": "payment-hooks", "source": "Stripe", "path": "/hooks/payment", "received_at": "2026-04-24T10:34:00Z" }
POST REQUEST TO YOUR ENDPOINT WITH THIS STRUCTURE:
{ "event": "email.received", "inbox": "staging-qa", "from": "app@yourapp.com", "subject": "Welcome to YourApp", "received_at": "2026-04-24T10:32:00Z" }
SMS EVENT:
{ "event": "sms.received", "inbox": "sms-qa-inbox", "from": "YOBANK", "message": "Your OTP is 483920. Valid for 10 minutes.", "received_at": "2026-04-24T10:33:00Z" }
WEBHOOK EVENT:
{ "event": "webhook.received", "project": "payment-hooks", "source": "Stripe", "path": "/hooks/payment", "received_at": "2026-04-24T10:34:00Z" }
SETUP
Connected in Three Steps
- 01
Go to Integrations
From your Sandbox account, navigate to Integrations and select Custom Webhook. Enter the endpoint URL for your custom webhook alert setup.
- 02
Choose your Endpoint and Inboxes
Confirm the endpoint URL, then choose which Sandbox inboxes and projects should trigger a POST request to it.
- 03
Test and Confirm
Send a test payload to confirm your endpoint receives and accepts it. Save — webhook delivery starts immediately.
USE CASES
Your systems, connected to every Inbox Event
Internal dashboard updates on every email received
Connect a custom webhook to your internal monitoring dashboard. Email sandbox alerts in Webhook fire a JSON payload whenever an email lands in staging — keeping your dashboard in sync with your test environment in real time.
CI/CD pipeline asserts on delivered OTPs
Your test suite triggers an SMS OTP flow, then uses SMS alerts in webhook from the sms.received payload to assert delivery — no manual checking, no flaky polling.
Custom alerting pipeline for failed deliveries
Route failed email events and SMS alerts in webhook straight into your own alerting system — PagerDuty, Opsgenie, or an internal tool — instead of relying on a chat platform your team may not use.
Sync Sandbox events into your own data warehouse
Forward every inbox event to an ingestion endpoint and log it alongside your other application events, for reporting or long-term analysis outside of Sandbox.
FAQ'S
The things developers ask about Custom Webhooks
What does the JSON payload look like?
Every payload includes an event type, the inbox or project it came from, source details, and a timestamp. The exact structure varies slightly by event type (email, SMS, or webhook) — see the docs for the current schema.
Can I verify that a request actually came from Sandbox?
Yes. Every outbound request includes a signature header you can verify against your webhook secret before trusting the payload.
Is there a limit to how many events can be sent to my endpoint?
Limits are based on your plan. All plans include a free tier suitable for staging and QA workflows.
Does Sandbox retry if my endpoint is down?
Yes. Failed deliveries are retried with backoff for a limited period. If your endpoint stays unreachable, the event remains visible in your Sandbox inbox regardless.
Can I connect more than one custom webhook endpoint?
Yes. Add as many custom webhook endpoints as you need, each scoped to its own set of inboxes and projects.
Can I disable a custom webhook temporarily without deleting it?
Yes. Pause the integration from the Integrations page at any time — no events are lost, they just stop being forwarded until you resume it.
GET STARTED
Your team shouldn't have to watch the inbox. Set up email sandbox alerts in Webhook once.
Connect Slack, Discord, Teams, Telegram, or your own endpoint. Every inbox event fires an instant notification — from the moment you connect.
What you get on Free:
Five integration options
Alerts on every channel - email, SMS, webhook
Connect in minutes
Free forever on basic plan