When To Use HTTP Interceptor
Use HTTP Interceptor when you want to:- inspect requests and responses in real time
- debug browser, mobile, emulator, terminal, or Node.js traffic
- verify whether an issue is in the client, proxy, or backend
- capture traffic for sessions, HAR analysis, or later mocking
Choose Your Interception Setup
Browser Extension
Best for browser-only workflows and the fastest setup.
Desktop App
Best for mobile apps, emulators, localhost, terminal tools, Node.js, and system-wide traffic.
First Success Path
Pick Browser Extension Or Desktop App
Use the Browser Extension for browser-based traffic. Use the Desktop App when you need proxy-based interception outside the browser.
Complete The Matching Setup Guide
Follow one setup path and make sure the browser, device, or runtime is correctly connected to Requestly Interceptor.
Confirm Traffic Is Visible
Open the network table or browser interception view and verify requests appear before moving on to rules or mocks.
Explore By Runtime
Desktop Browsers
Connect Chrome, Firefox, Edge, and similar browsers through the Desktop App.
Android Devices
Intercept traffic from Android phones and tablets.
Android Emulators
Capture traffic from Android Studio emulators.
iOS Devices & Simulators
Set up iPhones, iPads, and iOS simulators.
Node.js
Debug server-side requests from Node.js applications.
Terminal & CLI Tools
Inspect cURL, scripts, and other command-line network activity.
After Traffic Starts Flowing
Create Rules
Modify intercepted traffic once you know what needs to change.
Capture Sessions
Save traffic and debugging context for sharing, replaying, or mock creation.
Import HAR Files
Analyze previously captured network data inside Requestly Interceptor.
Fix Interception Issues
Use the troubleshooting path for certificate, localhost, proxy, or device issues.