Inspect outbound traffic
Start an isolated shell, make a request with your usual tool, and inspect the captured headers and body in the desktop or terminal UI.
Wiretap documentation
See the requests your tools send, keep public webhook deliveries while your desktop is offline, and replay or reshape payloads locally.
Pick a workflow
Section titled “Pick a workflow”Receive public webhooks
Run the relay on a public server. It queues deliveries while your desktop is offline and sends them through an outbound tunnel after reconnecting.
Compose and replay
Build an HTTP request by hand, import JSON, continue from captured traffic, or turn a source record into an editable draft.
Transform payloads
Use sandboxed local JavaScript to change or reject intercepted requests, responses, webhook deliveries, replays, and compose recipes.
One local history, three interfaces
Section titled “One local history, three interfaces”The desktop GUI, terminal UI, and CLI use the same local SQLite store. Choose the interface that fits the moment without splitting capture history between tools.
Wiretap is self-hosted. Outbound interception stays on your machine, while public webhook ingress runs through your own wiretap-relay deployment.