You can test webhook delivery end-to-end without producing real platform events. The dashboard fires fully-signed sample deliveries on demand.
Send a test event
Each webhook endpoint has a Send test event button. Pick any event type the endpoint is subscribed to and a sample payload is dispatched with a real signature, a real delivery id, and the same headers a production delivery would carry. Test events are flagged in the deliveries view so they don’t pollute your real-event metrics.
Test events go through the same retry machinery as production. If your endpoint returns non-2xx, the test delivery is retried just like the real thing.
Receive deliveries locally
Awardee needs an HTTPS URL reachable from the public internet. For local development, tunnel your local port through a hosted endpoint.
ngrok
Cloudflare Tunnel
Tailscale Funnel
ngrok http 3000
# Forwarding https://abcd-1234.ngrok-free.app -> http://localhost:3000
https://…ngrok-free.app URL into the webhook config.cloudflared tunnel --url http://localhost:3000
# 2026-05-23T10:14:33Z INF +-----------------------------------------+
# 2026-05-23T10:14:33Z INF | https://random-words-1234.trycloudflare.com |
# 2026-05-23T10:14:33Z INF +-----------------------------------------+
tailscale funnel 3000
# Available on the internet:
# https://laptop.tail-net.ts.net/
Verifying locally
The signing secret on a test webhook is the same as a production webhook — there’s no test-mode secret. Use it directly in your verification code. See Signing.
Log the raw X-Awardee-Signature header and the request body bytes in development. Most signature-verification bugs come from a framework silently reformatting the body before your handler reads it.
Inspecting deliveries
The dashboard’s deliveries view records every attempt: timestamp, HTTP status, response body (truncated to 4 KiB), response time, and the event payload. Each row is replayable — useful when you’ve fixed a handler bug and want to re-process the events that failed in the meantime. 
