
A run against a deliberately buggy Stripe handler: two findings, exit 1.
How it works
1
Capture
Point a provider at your capture URL. Every request is stored as received: method, path, headers and the exact body bytes.
2
Prove
Select captured events and start a run. Your paired agent sends them to your handler as Once, Twice, Shuffled, Late, Retry after error, Tampered, Unsigned, Burst and Slow budget.
3
Read the verdict
Each finding names the scenario, the deliveries that broke the rule, what happened, why it matters for that provider, and how to fix it.
4
Keep it in CI
webhooktrap test runs the same scenarios from fixture files in your repository and exits non-zero when a finding is at or above --fail-on.Where to start
Quickstart
Get a capture URL without an account, capture an event, pair the agent and read your first finding.
Core concepts
Projects, captures, guest sessions, the agent, runs, scenarios, findings and packs.
Test in CI
Run
webhooktrap test in GitHub Actions and fail the build on High and above.Self-host
Run your own instance with Docker Compose.