AI 产品解读Intercept, modify, and mock HTTP(S) network requests and responses directly in the Chrome browser
Enables web developers and QA engineers to modify network traffic (redirect URLs, modify headers, inject scripts, mock API responses) without setting up a proxy server, avoiding VPN issues and latency. Allows frontend development when backend APIs aren't ready, testing local JS/CSS changes on production sites, and overriding REST/GraphQL API responses.
User installs the extension, creates HTTP rules (redirect, headers, script injection, mock API responses) via the extension popup or the Requestly web app at app.requestly.io. Rules are stored locally in chrome.storage.local. When browsing, the service worker intercepts matching requests using declarativeNetRequest and webRequest APIs, applies the configured rules, and optionally records sessions for replay. The extension integrates with the Requestly web app for advanced rule management, team collaboration, and cloud sync.
URL redirect rulesHTTP header modification (request and response)JavaScript and CSS injection into pagesREST and GraphQL API response mockingAPI request/response body and status code overrideSession recording and replay
- 目标用户
- Web developers / QA engineers / Frontend developers / DevOps engineers / API testers
- Source code is heavily minified making detailed logic analysis difficult
- Could not definitively determine if the web app UI (popup React app) requires login or renders locally without auth
- The devtools/index.js is 1.69MB minified - deep inspection was not feasible within tool budget
付费分析未识别到付费功能
No payment-related code found in the extension source: no premium/subscription/billing/pricing/upgrade/stripe keywords detected. The 'checkout' matches are all from the rrweb session recording library (checkoutEveryNms, isCheckout parameters) which is session replay checkpoint terminology, not payment. The extension is open source (https://github.com/requestly/requestly/). No feature gating, license checks, or payment UI found in the extension code. The destination service (Requestly/BrowserStack) likely has paid team/enterprise plans, but the extension itself does not gate features behind payment.
- 置信度
- 70
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 是
- 登录理由
- The extension's core rule-application engine works locally without login (rules stored in chrome.storage.local). However, the extension heavily integrates with the Requestly web app at app.requestly.io for session recordings (SESSIONS_URL), rule management UI, team collaboration, and cloud sync. The app.cs.js content script injects on requestly domains to bridge the extension and web app. Session recording drafts open at app.requestly.io/sessions/draft/{id}, and the externally_connectable manifest connects to BrowserStack domains. Login to the destination service (Requestly web app) is required for the full workflow including cloud features, session replay, and team collaboration.
Muito boa para debug de APIs
Использую приложение как рабочий инструмент регулярно. Помогло обойти проблему с longurls при попытках подменить response body на винде. Мне все нравится, удобное.
Very good, I hope there will be a free version soon
Great tool
Great tool, I use it mostly every day. It helps a lot for modifying my test cases.
Very handy tool for frontend QA, testing and development overall
Can't say enough great things about this tool. We have a ton of complex data at work. Whether it be complex user data, specific error scenarios that just don't happen that often, or anything else I need from an API to prove to myself that something on the UI is working correctly, I always turn to Requestly to get me through it!
Very handy tool for frontend development!!
Useful tool for the QA purposes to modify BE responses
I use it to mock API calls to my servers. Sometimes I don't have a service running locally or the data that I have is not good enough for a complex page to render as expected. Here is where Requestly comes in. I mock responses with data that I want to have in my front end, and I do not need to worry about bad data in database, or an API that is not functioning correctly. I can mock headers as well during app's request. It is super useful for front end development. Responses can be dynamic as well, such as :id that is returned from the API. Solved my pain working with microservices and bad local data!