4 items
Mocks api responses for AJAX (XHR) requests. (Postman for Frontend) This is essentially built to increase productivity in frontend development. Made for developers, it lets users to define rules (url, method and mock response) to respond to AJAX calls. Supports all common libraries like axios, superagent, XMLHttp, fetch etc. Response can be a JSON object or an error. It includes a JSON formatter to automatically convert your response in proper json format. Each rule can be individually turned on/off to apply mocking. There's a global power switch to turn off mocking all the rules at once. The JSON object maker lets users to make the object in JS syntax and the formatter will convert it into valid JSON object with inverted commas and no trailing commas etc. some other response types are also supported in the editor like html, xml or text. this can be changed from response headers which by default is set to application/json Features: 1. Urls can be absolute complete paths or regex enabled. 2. Labels for rules, so user can add different versions of same api 3. Delay in response 4. Test your app with success and error responses. 5. Add response headers along with mock response in the rule. Steps for Users - 1. Define the api url, method, response JSON or error msg to be mocked. 2. Refresh the project and the ajax / fetch request will be mocked. Mocked url will disappear from network tab and appear in console if rule matches. For any query or bug report or feature request - reach out to nerdynbirdy@gmail.com. This extension is made with love for fellow developers. If this helps you, support us with good reviews :)) Let's build stuff.
Jun 8, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.