ValDam REST Logger
Language: EN ES
Chrome Extension · Manifest V3

Log and inspect all your REST API requests

ValDam REST Logger intercepts fetch(), XMLHttpRequest and WebSocket traffic in real time, with image preview, JSON formatting, performance charts, mock/modify rules and HAR export.

⬇ Install from Chrome Web Store Manual installation
  • fetch · XHR · WSRequest types captured
  • HAR 1.2HAR 1.2 export
  • $0100% free & MIT licensed

Features

Everything you need to debug APIs from DevTools.

🔍 Full capture

Intercepts fetch(), XHR and WebSocket. Captures headers, bodies, status codes and timing for every request.

🖼️ Image preview

Detects and previews images in requests and responses, including files inside FormData (great for face recognition apps).

📊 Performance charts

Latency timeline, waterfall of your last 50 requests and status-code distribution with P50/P95/P99 percentiles.

🧪 Rules Engine (Mock/Modify)

Change headers, body or URL before sending; mock responses with simulated delay using glob or regex patterns.

🔁 Replay & compare

Replay any edited request and compare two requests side by side with a diff of headers, body and response.

📦 HAR & session export

Export to standard HAR 1.2 (Postman, Charles, DevTools) and save/import full sessions as JSON.

Installation

From the official store or in developer mode.

  1. Install from the Chrome Web Store

    Click "Add to Chrome" on the extension listing. This is the fastest and safest way.

  2. Open DevTools

    Press F12 or Ctrl+Shift+I on any tab and select the "ValDam REST Logger" panel tab.

  3. Enable the debugger

    The 🐛 button connects automatically via CDP so full response bodies can be captured.

Note: the first time you open DevTools, Chrome shows a banner saying the extension is debugging the browser. This is normal and required to capture response bodies.

Frequently asked questions

The "ValDam REST Logger" tab does not appear

Close every DevTools window, reload the extension at chrome://extensions and open DevTools again with F12.

Why can't I see response bodies?

Make sure the 🐛 button is ON. Without the Chrome debugger only headers and statuses are captured (a Manifest V3 limitation).

What is the "started debugging this browser" banner?

It is Chrome's native message when using chrome.debugger and cannot be avoided. It disappears when you disconnect the debugger (🐛 OFF).

Does the extension send my data anywhere?

No. Everything is processed and stored locally in your browser through chrome.storage.local. No telemetry, no external servers.

Does the debugger disconnect by itself?

The MV3 service worker suspends after ~30s of inactivity; the debugger reconnects automatically when there is activity.

Privacy Policy

Last updated: August 2026

Data we handle

The extension captures network traffic (requests and responses) only inside your browser, to show it to you in DevTools. Nothing leaves your machine: no servers, no analytics, no trackers.

Local storage

Captured sessions, your mock/modify rules and your preferences (debugger toggle, filters) are saved in chrome.storage.local on your device only. Everything is deleted when you press "Clear" or uninstall the extension.

Support form

If you contact us through the form on this page, we store your name, email and message solely to answer your inquiry, in our SQLite database on the support server. We never share it with third parties or use it for advertising.

Requested permissions

"webRequest" and "debugger" to capture traffic; "storage" to save sessions; "scripting" to replay modified requests. Access to all URLs is required because the extension works wherever you debug.

Support

Found a bug or have a suggestion? Write to us and we will reply by email.