6 items
Intercept and modify fetch/xhr requests and responses on browser Receptor helps you intercept, inspect, and modify fetch and XHR requests and responses directly in Chrome, making it easier to debug APIs, test frontend behavior, and simulate backend changes without touching server code. Built for developers, QA engineers, testers, and API integrators, Receptor gives you fine-grained control over browser network traffic in real time. You can update request headers, response headers, request bodies, response bodies, query parameters, status codes, and delays using flexible matching rules based on URL, HTTP method, and other request details. Receptor is useful for API testing, frontend debugging, mocking responses, validating error handling, simulating alternate server behavior, and testing edge cases before release. Instead of changing your backend or setting up a separate proxy, you can modify live browser traffic directly where your application runs. What you can do with Receptor: - Intercept and modify fetch and XMLHttpRequest traffic - Edit request and response headers - Replace or update request and response bodies - Rewrite query parameters before requests are sent - Change response status codes - Simulate delayed responses and test loading states - Organize rules with scenarios and groups - Import and export local configurations - Create advanced request and response transformation workflows Receptor is designed for modern web development workflows and is especially helpful when working with SPAs, REST APIs, internal tools, staging environments, and frontend-heavy applications that rely on dynamic network requests. Use Receptor to: - Debug API integrations faster - Test frontend changes without backend deployment - Simulate success, error, and edge-case responses - Validate request payloads and headers - Reproduce bugs caused by specific API responses - Improve QA and regression testing in the browser If you need a flexible browser extension for request interception, response modification, API debugging, frontend testing, and network mocking, Receptor gives you a practical way to control fetch and XHR traffic directly inside Chrome.
Jun 2, 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.