Skip to main content
HTTP Dumps

See exactly what the request contained

You're building a webhook, a callback or an API client, and you need to see what actually goes over the wire. Send the request to Buggregator: you get the method, URL, headers, cookies, form data and uploaded files — and a cURL command to send it again. No separate service like webhook.site.

Get started Any HTTP client · port 8000
127.0.0.1:8000

A captured request with its headers, query, form data and files. Example data.

Everything that came over the wire

Build and debug webhooks and API calls without logging code or a third-party inbox.

📨

The whole request

Method, path, host, query parameters, headers and cookies.

📝

Form data and files

Submitted fields and uploaded files — download any file from the UI.

🔁

Replay with cURL

Every request as a ready cURL command: URL, headers and body. Paste it in a terminal and the same request arrives again. Uploaded files are named, not attached.

🪝

Webhook development

Point the sender at Buggregator and see exactly what it sends, before you write the handler.

🔎

Search

Find requests by host, method or URL.

🧭

Need the response too?

HTTP Proxy records request and response for outgoing calls; Mock Server answers with a response you define — and each call shows up here.

Setup in 60 seconds

No registration. No account. Start it and point your app at it.

1

Start Buggregator

HTTP dumps arrive on port 8000, the same port as the UI. One file, about 40 MB, installed with one command. Prefer containers? Use the Docker tab.

$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh
$ HTTP_ADDR=127.0.0.1:8000 \
  SMTP_ADDR=127.0.0.1:1025 \
  VAR_DUMPER_ADDR=127.0.0.1:9912 \
  MONOLOG_ADDR=127.0.0.1:9913 \
  PROXY_ADDR=127.0.0.1:8080 \
  ~/.local/bin/buggregator

El script elige el archivo para tu procesador: Intel/AMD o ARM.

Un solo archivo para Linux, macOS y Windows, de unos 40 MB. No hace falta instalar nada más.

Esta línea lo deja solo en este equipo. Sin los ajustes *_ADDR escucha en todas las interfaces de red →

¿Prefieres no ejecutar un script? Descarga el archivo tú mismo →

2

Mark the request as a dump

Send any HTTP request to Buggregator and mark it in one of two ways: the user name http-dump in the URL, or the X-Buggregator-Event header. A third-party service on the internet can only reach Buggregator at a public address.

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

See the request

Open http://127.0.0.1:8000. The request appears with its headers, body, files and a cURL command. In Docker Compose, use the service name instead of 127.0.0.1.

Works with anything that speaks HTTP

No SDK. Change the URL, add a user name or a header.

curl— http://http-dump@127.0.0.1:8000/...
PHP— Guzzle, Laravel HTTP, Symfony HttpClient
JavaScript— fetch, axios (X-Buggregator-Event header)
Webhook senders— set the webhook URL to Buggregator
Any language— any HTTP client that can set a URL or a header

Ready to try it?

One command to start. No account needed.

Also built into Buggregator