Guides
Test Delivery
Send a real event through the real delivery pipeline, straight from the dashboard —
no curl, no API key, no code — to confirm an Endpoint is wired up correctly
before it ever sees production traffic.
What makes it a "test" delivery
Same pipeline, flagged
A test event is written, fanned out, signed, and delivered through the exact same path as any other event — fan-out, HMAC signing, retries, everything. The only difference: the outbound HTTP request carries a
webhook-test: true header, so your subscriber's server can tell it apart from real traffic if it wants to.No API key needed
Because you're already logged into the dashboard, sending a test event doesn't require pasting in an API key — it goes through the management API using your existing session.
Shows up in your delivery logs
The resulting delivery attempt appears in Delivery Logs exactly like any other, so you can inspect the HTTP status, response body, and latency your Endpoint actually returned.
Dashboard → Applications → your app → Send Test Event
This is the fastest way to validate a new Endpoint or a Subscriber's changed URL —
no need to fabricate a real order or wait for real traffic to confirm it works.