Overview
Intercept & inspect XHR/fetch calls β headers, payloads, timing, CORS & auth errors. Essential for dev & QA. By Cloud Geeks.
π¬ **A Focused XHR/Fetch Inspector Inside Chrome DevTools** API Inspector adds a dedicated panel to Chrome DevTools for capturing, inspecting, and exporting the XHR and fetch requests a page makes β without the noise of the full Network tab. Filter by URL or method, read request and response bodies, and export what you captured as HAR, JSON, or a ready-to-run cURL command. And unlike the native tools, API Inspector redacts your secrets before you share. ββββββββββββββββββββββ β¨ **KEY FEATURES** π‘ **Real-Time Request Capture** β’ Captures every XHR and fetch() call the inspected page makes β’ Updates live as requests fire β’ Shows method, URL, status code, and request duration β’ Colour-coded by HTTP method (GET, POST, PUT, PATCH, DELETE) β’ Status indicators: success (2xx/3xx) vs error (4xx/5xx) π **Request & Response Detail** β’ Request tab: full URL, method, timestamp, and request body β’ Response tab: status, duration, and response body β JSON auto pretty-printed β’ Headers tab: full request and response header sets π― **Filtering** β’ Filter by URL (substring match) β’ Filter by HTTP method β’ Clear filters to return to the full capture πΎ **Export & Safe Sharing** β the reason to install β’ Export the shown requests as **HAR 1.2** (the industry-standard format) β’ Export as **JSON** for custom processing β’ **Copy any request as a runnable cURL command** β’ **Secret redaction, on by default** β Authorization, Cookie, Set-Cookie, API keys and other sensitive headers are replaced with [REDACTED] in every HAR, JSON, and cURL output β’ Exports respect your active filters β you export only what you filtered to ββββββββββββββββββββββ π **WHY THE REDACTION MATTERS** Chrome DevTools can copy a request as cURL and export HAR too β but it embeds your cookies, Authorization headers, and tokens in plaintext. Paste that into a bug ticket, a pull request, or a Slack thread and you've just leaked a live credential. API Inspector redacts those secrets by default, so the HAR you attach and the cURL you paste are safe to share. The redaction set is a sensible default for common auth headers; the capture itself is never altered. ββββββββββββββββββββββ π **HOW IT WORKS** API Inspector lives inside Chrome DevTools β not in a popup or sidebar. 1. **Open Chrome DevTools** (F12 or right-click β Inspect) 2. **Click the "API Inspector" tab** 3. **Reload or interact with the app** to trigger requests 4. **Watch requests appear** in real time 5. **Click any request** to inspect headers and body 6. **Filter, then export** as HAR/JSON or copy as cURL β with secrets redacted ββββββββββββββββββββββ π‘ **USE CASES** **Frontend developers** β verify request payloads and auth headers are correct; see what a third-party script sends in the background. **Backend developers** β confirm exactly what the frontend sends before it reaches your server; compare expected vs. actual request shape during integration. **QA engineers** β capture API traffic during a test run and attach a **redacted HAR** to the bug ticket, with no credentials to scrub by hand. **Support & security** β hand a customer a cURL that reproduces a call, or a HAR of a failing flow, without exposing their session token. ββββββββββββββββββββββ π οΈ **COMPARED TO THE NETWORK TAB** | Feature | Native DevTools | API Inspector | |---|---|---| | XHR/fetch-only view | Mixed with all resources | Dedicated | | JSON body pretty-print | Manual | Automatic | | HAR export | Yes (sanitised since Chrome 130) | Yes (HAR 1.2) | | JSON export | No | Yes | | Copy as cURL | Yes β **secrets in plaintext** | Yes β **secrets auto-redacted** | ββββββββββββββββββββββ π **PRIVACY & SECURITY** β’ β **Nothing leaves your browser** β captured traffic is never transmitted to any server β’ β **Local-only logs** β the extension keeps small usage and error logs in chrome.storage.local to improve reliability; these stay on your device and are never sent anywhere β’ β **DevTools only** β the panel is accessible only while DevTools is open β’ β **Session-scoped capture** β captured traffic clears when you clear it or close DevTools β’ β **Passive** β API Inspector reads traffic; it never modifies the requests the page makes ββββββββββββββββββββββ π **SUPPORT** β’ π§ Email: support@cchk.info β’ π Website: https://extensions.cchk.info/api-inspector β’ π Privacy Policy: https://extensions.cchk.info/api-inspector/privacy ββββββββββββββββββββββ π’ **Built by Cloud Geeks** β a division of **Ganda Tech Services** IT Support & Cloud Solutions for Sydney businesses and beyond. π Visit us: https://cloudgeeks.com.au | https://g-t-s.com.au
0 out of 5No ratings
Details
- Version1.0.9
- UpdatedOctober 19, 2026
- Size28.98KiB
- LanguagesEnglish
- DeveloperAshish GandaWebsite
18 Patel St Rouse Hill, NSW 2155 AUEmail
ash@eawesome.com.auPhone
+61 433 309 677 - TraderThis developer has identified itself as a trader per the definition from the European Union and committed to only offer products or services that comply with EU laws.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site