Test the delivery before it becomes an incident.
Build an event, validate its contract, sign it, and inspect the delivery evidence. Protected sends and replays use the shared PlatPhorm key.
Start a webhook test
Read the guide →Build
Create a test event
Generate a valid event envelope from a template, then inspect the exact payload.
Verify
Check a signature
Generate or verify HMAC-SHA256 and SHA512 signatures with transient secrets.
Inspect
Review delivery evidence
See real attempts, latency, retries, redaction, and trace state—or an honest degraded state.
One clear workflow
From payload to evidence
The complete lifecycle stays available, but the common path is four steps.
Open WebhookLab- 1
Define event type
Name the event, version it, and wrap it in the PlatPhorm event envelope.
- 2
Define event contract
Attach JSON Schema or an AsyncAPI-compatible event contract before delivery.
- 3
Sign payload
Build the canonical string and HMAC header without storing the raw secret.
- 4
Inspect attempts
Review status, latency, retry decision, redacted request/response summaries, and trace span.
Everything remains reachable
Webhook tools
Connected to the PlatPhorm mesh
Working integrations: MCP Gateway, platphormctl. Unwired handoffs report degraded status instead of fake success.