DevKit – API Debugger & Network Inspector
Overview
Capture your web app's real API calls, then edit, resend, and save them, gRPC-Web included.
Your app just made the call you need to debug. Rebuilding it in a separate client means copying the URL, the headers, the token, and the body by hand, and if the payload is gRPC-Web or Protobuf you cannot read it at all. DevKit closes that gap. Record a tab, click an entry in the list, and it is already editable: method, URL, query parameters, headers, and body, with the response beside it. Change something, press Send, and the result lands in the same list next to the original so you can compare the two. What only an in-browser tool can do • Capture what your app really sent, from the page itself, without opening DevTools. • Decode gRPC-Web frames and turn Protobuf field numbers into names using your own .proto files. Import them once into the workspace; imports between files resolve on their own, and the message types are picked from the gRPC path. • Read GraphQL operations, WebSocket frames, and Server-Sent Events in the same panel, and send a WebSocket frame back through the page's own connection. • Compare an original response with a later one field by field, ignoring the paths and headers you choose. What you would expect from an API client • Collections with nested folders, colours, drag-and-drop, and folder-level auth that everything inside inherits: bearer token, basic credentials, or an API key in a header or query parameter. • Environments with variables, masked secrets, and {{placeholders}} filled in when you send. • An editor with Params, Headers, Body, Auth, Runs, and Tests tabs. Body formats: JSON with formatting, raw text, form URL encoded, multipart with file attachments, GraphQL with separate query and variables, and gRPC-Web. • Run history for every saved entry: status, duration, assertion outcome, any run promoted to a baseline, and a diff between two runs. • Assertions, regression baselines, scenarios that chain several steps and pass values along, and data-driven testing over a table of variables. • Mock, block, delay, or override matching traffic while recording. Bring what you already have • Paste a cURL command, including Chrome's own "Copy as cURL", and get somethin • Import a Postman v2.x collection with its folders, bodies, auth, and collection variables. Postman scripts are not run. • Export any single entry as JSON with its full response and timing, then impor to a colleague. • Copy an entry out as cURL, JavaScript fetch, or Go net/http. Your data stays in your browser DevKit attaches to a tab only after you press Record there, and Chrome shows its debugging banner for as long as it does. Captured traffic, saved collections, and anything you type stay in Chrome's local extension storage. There is no account, no sync, no analytics
0 out of 5No ratings
Details
- Version0.2.0
- UpdatedNovember 9, 2026
- Offered byAntz
- Size134KiB
- LanguagesEnglish
- Developer
Email
pxbao.itus@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
DevKit – API Debugger & Network Inspector has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
DevKit – API Debugger & Network Inspector handles the following:
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, please open this page on your desktop browser