Request Logger

⚡ Capture webhooks and HTTP requests locally in VS Code - with private endpoints and a live JSON dashboard.

🚀 Start here

1. Open VS Code and press Ctrl+Shift+X to open Extensions.
2. Search for Request Logger and install the extension.
3. Open Request Logger from the Activity Bar and choose Open Request Logger Dashboard to start the local server.
4. Copy the generated endpoint URL
5. Send a POST request to it
6. Inspect the payload in the dashboard

🤔 Why this exists

When a webhook, callback, or integration sends data to your application, the fastest way to understand a failure is to inspect the exact request that arrived.

That usually means deploying a temporary endpoint, sharing payloads with a hosted inspector, or adding one-off logging to a service that is still under development.

Request Logger gives you a private capture endpoint and a request dashboard directly inside VS Code.

🎁 What you get

🔗 A private capture endpoint

Every dashboard session receives an unguessable session id. The generated URL contains that id, allowing Request Logger to show each session only its own captured requests.

Copy the endpoint from the Active Endpoint panel and paste it into the service, script, or webhook configuration you are testing.

🧭 A request activity dashboard

Captured requests appear newest first. Each request includes:

• A formatted timestamp and relative time
• An expandable JSON body
• A copy action for the payload
• Individual expand/collapse controls
• An Expand all or Collapse all action for the full list

🔄 Optional auto-refresh

Enable Auto-refresh when you are waiting for requests from another system. The dashboard polls every five seconds, pauses while the browser tab is hidden, and preserves the preference after a page reload.

🧪 Test the endpoint locally

Use Test Connection to send a sample request to the active endpoint. The result appears below the action controls and dismisses automatically.

🔐 Privacy and security

Request Logger is local-first, but its capture endpoint is public while the tunnel is running.

• Treat the complete endpoint URL as a secret.
• Anyone with the URL can send requests to it.
• Anyone with the session id can read that session's captured requests.
• The dashboard API is restricted to localhost and is not exposed through the tunnel.
• Requests are stored locally in the extension's VS Code global storage directory.
• Sessions expire after six hours of inactivity and are bounded by count, size, and request-volume limits.

Do not place credentials, access tokens, or other secrets in test payloads unless you are working in a controlled environment.

📦 What happens to your data

• Request Logger starts its local server and secure tunnel automatically when you open the dashboard.
• Captured requests are stored locally in VS Code extension storage.
• Each dashboard session receives its own private session endpoint.
• Sessions survive a page refresh while the extension is running.
• Sessions expire after a period of inactivity and are bounded to protect local resources.
• The dashboard API stays local and is not exposed through the public tunnel.

If a request does not appear, confirm that the complete endpoint URL is being used and then select Refresh or enable Auto-refresh.

_{Made for developers who need to see the request, not guess what happened.
Request Logger is an independent open-source project.}