API Failure Investigator

Turn a web API failure into an evidence-backed bug report.

API Failure Investigator turns a broken web request into a bug report your backend team can act on. Open the side panel, click Record, and reproduce the problem. The extension captures the API calls and console errors of that one tab, highlights failed and slow requests, and groups what happened around each failure into an incident with a likely root cause. Features • Capture Fetch/XHR traffic, status codes, headers, bodies and timing for the tab you choose • Failures and slow calls are surfaced automatically, with related requests and nearby console errors grouped together • Inspector with Issue, Request, Response and Headers views; secrets are hidden by default • Copy a report as Markdown, cURL, fetch() or JSON. Credentials such as Authorization headers, cookies, tokens, API keys and passwords are masked before copying • Tests: edit a captured request (URL, headers, body, auth) and resend it from the page to confirm a fix. Hidden secrets are only reused for the site they were recorded on • Optional feedback form for bugs, ideas and support Why Chrome shows "started debugging this browser" Capture uses Chrome's debugger permission, the only way an extension can read response bodies and console errors. Chrome shows its banner while recording, and it closes a few seconds after you stop. Click Stop, cancel the banner, or close the tab to end capture at any time. Privacy Captured traffic stays in memory on your device and is deleted when you clear it or close the browser. Nothing is sent anywhere unless you press Send in the feedback form, or Send in the Tests view, which resends your edited request to that request's own server. No ads, no data sale. Full policy: https://sites.google.com/view/api-investigator-privacy Masking is pattern-based: review a report before sharing it.