Requestly HTTP Interceptor.
Open-Source HTTP Interceptor & Mocking Tool
Loved by 300k+ developers — intercept, modify, mock, and debug HTTP(S) traffic from your browser and desktop apps.
Part of the Requestly ecosystem — Requestly API Client · HTTP Interceptor · HTTP Interceptor Desktop · Docs
Download
·
Documentation
·
Report Bug
·
Discussions
·
Community
🚀 What is Requestly HTTP Interceptor?
Requestly HTTP Interceptor is an open-source HTTP interception and traffic debugging tool that helps developers intercept, inspect, monitor, and modify HTTP(S) traffic directly from browsers and desktop apps.
It supports powerful debugging workflows including request/response modification, API mocking, traffic inspection, and environment overrides without requiring complex proxy or VPN setup.
Trusted by 300,000+ developers and 11,000+ companies worldwide.
✨ Features
🌐 HTTP Interceptor
Intercept, monitor, and modify HTTP(S) requests and responses in real time.
📚 Docs: https://docs.requestly.com/general/http-interceptor/overview
Supported capabilities
- Redirect URLs and environments
- Map local files and remote resources
- Modify request and response headers
- Override API request and response bodies
- Inject custom JavaScript into webpages
- Debug and inspect network traffic
- Capture traffic from browsers, mobile apps, and desktop apps
Common use cases
- Redirect production traffic to local or staging
- Test feature flags and edge cases
- Override APIs during frontend development
- Replace analytics or third-party scripts
- Simulate backend failures and latency
⚡ API Mocking
Build and test frontend applications without waiting for backend APIs.
📚 Docs: https://docs.requestly.com/general/api-mocking/api-mocking
Features
- Local API mocking
- Cloud-hosted mocks
- Static & dynamic response overrides
- GraphQL request targeting
- Bulk mock generation from sessions
- Mock APIs in Cypress, Playwright, Selenium, and CI pipelines
Supported workflows
- Frontend parallel development
- E2E testing
- QA & staging simulations
- Offline development
- Contract testing
🔄 1-Click Imports
Easily migrate existing configurations from other tools.
Supported imports
- Charles Proxy
- ModHeader
- Resource Override
📚 Docs
🏁 Getting Started
Install Requestly HTTP Interceptor
Pick the install that matches how you work — a lightweight browser extension for in-browser interception, or the desktop app for system-wide traffic capture.
🌐 Browser Extension
Install Requestly directly into your browser to start intercepting and modifying HTTP(S) traffic in seconds.
🖥️ Desktop App
Use the desktop app to capture traffic across browsers, mobile devices, and any desktop application — ideal for debugging, mocking APIs, and sessions.
The desktop app source code lives in a separate repo: requestly/http-interceptor-desktop-app.
🧑💻 Development
This repository contains:
- Browser Extension (
browser-extension/) — Chrome, Firefox, Edge (Manifest V3)
- Web App UI (
app/) — the dashboard at app.requestly.com
- Core Traffic Interceptor Logic
Local Setup
Follow the setup guide:
👉 Getting Started
Related Repositories
🤝 Contributing
We welcome contributions from the community.
Whether you're fixing bugs, improving docs, or building new features, your contributions help make Requestly better for developers everywhere.
How to contribute
- Explore open issues
- Read the contributing guidelines
- Submit a pull request
- Join the community discussions
Useful links
🛟 Support & Resources
A note on this repository
The open-source source code for the Requestly HTTP Interceptor extension and web app lives here at requestly/interceptor. Previously this code lived under requestly/requestly; that URL is now the community and issue tracker for the Requestly API Client.
The HTTP Interceptor remains fully open source and actively maintained. Contributions, bug reports, and feature requests are welcome here.
❤️ Built for Developers
Requestly is built to make debugging and testing faster and simpler.
From HTTP interception and API mocking, Requestly gives developers everything needed to debug and ship confidently.
Deferred / TODO before publishing
- Brand asset paths (
https://github.com/requestly/interceptor/blob/master/app/src/assets/img/brand/...) — verify these files exist in the new repo after the codebase migration
- Screenshot URLs (currently
github.com/user-attachments/...) — verify they remain accessible from the new repo context (user-attachments are organization-scoped, should be fine)
- Decide whether to keep
discussions link (current README has it; some teams disable Discussions to reduce triage surface)