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.

CUSTOM WEBHOOK INTEGRATION

Fire a Webhook on Every Sandbox Event To Any Endpoint You Choose

Connect Sandbox to your own systems. 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.

SET UP CUSTOM WEBHOOK

Works with any HTTP endpoint

Structured JSON Payloads

Active Immediately After Setup

WHY USE A CUSTOM WEBHOOK

Not every team works in Slack or Discord. Your tools are your tools.

Custom webhook integration is for teams who want Sandbox events to flow into their own systems — internal dashboards, monitoring tools, custom alerting pipelines, or any HTTP endpoint that can receive a POST request.

No platform dependency. No third-party required. Just a URL and a JSON payload your system can handle however you need.

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 you want events sent to.

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. Every email that lands in your staging inbox fires a JSON payload to your endpoint — 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 listens on your webhook endpoint for the sms.received payload to assert delivery — no manual checking, no flaky polling.

Custom alerting pipeline for failed deliveries

Route every failed email or SMS event 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.

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.