See a webhook's payload before you write the handler

1. Point the webhook at Buggregator

Buggregator takes HTTP events on port 8000, the same port as the UI. Use http-dump as the URL user name. The path is yours to choose. In Docker Compose, replace 127.0.0.1 with the Buggregator service name, for example buggregator.

# Your app sends webhooks or callbacks to this URL during development
WEBHOOK_URL=http://http-dump@127.0.0.1:8000/webhooks/orders

2. Check it with a test request

Before you wait for a real delivery, send one yourself.

curl 'http://http-dump@127.0.0.1:8000/any/path?foo=bar'

3. Or mark it with a header

If the sender cannot put a user name in the URL but can set a header, use X-Buggregator-Event instead.

curl 'http://127.0.0.1:8000/any/path?foo=bar' \
  --header 'X-Buggregator-Event: http-dump'

4. Read the payload

Open http://127.0.0.1:8000. The request shows its method, full URI, query parameters, form data, headers, cookies and uploaded files, which you can download. Search finds requests by host, method or URL.

Buggregator treats any HTTP request marked with http-dump, by user name or header, as a dump and stores it whole. A third-party service on the internet can only reach Buggregator at a public address, so a service in the cloud cannot call your laptop's 127.0.0.1. When you need the response from a real server too, use the HTTP proxy instead.