Capture the active tab's API traffic and turn it into a working API client with route-reveal.
Users
2
−1 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#367K
#277K among extensions
Version
0.1.0
updated 22 Jul 2026
Users
monthly, 3 months
Latest, 15 Oct 2026:2 usersMove the mouse over the chart for any month
Ratings count
monthly, 3 months
Latest, 15 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About route-reveal capture
Turn any website's undocumented API into working, tested code — just by browsing it.
Most APIs you need to integrate with were never meant to be public. There's no documentation, no OpenAPI spec, nothing but a bunch of XHR calls your browser makes while you use the site. Today that means opening DevTools, exporting a HAR file, and manually piecing together endpoints, headers, and auth by hand.
route-reveal capture skips all of that. Click Start, use the site normally — log in, click around, do whatever you'd do anyway — then click Done. The extension captures every API request and response your browser actually made (not just a guess at the shape of the API) and hands it to route-reveal, which turns it into:
- A working client script (Python, JavaScript, or TypeScript) written and tested against the real API
- An OpenAPI 3.0 spec and Postman Collection, generated directly from the captured traffic
- Plain-text cURL commands, one per request
- Optionally, an SDK in Java, C#, Go, PHP, Ruby, or C
Why use the extension specifically: it captures traffic from a tab you're already using, in your own logged-in browser session — no separate browser window, no re-entering credentials, no VPN or internal-network complications. If a site is behind a login, a corporate VPN, or otherwise isn't reachable from a cloud browser, this is the path that works.
What it needs: a route-reveal account (currently invite-only while in testing) and its API token, pasted into the extension once. From there, it's Start, browse, Done.
Permissions, plainly: the extension reads network traffic only on the tab you explicitly start a capture on (chrome.debugger — the only API that can read response bodies under Manifest V3), sends that traffic to your own route-reveal backend, and optionally shows a small on-page status control while capturing (permission requested per-site, only when you start a capture there — never a blanket grant). Nothing else is touched, and nothing runs in the background when you're not actively capturing.