API debugging, right in your browser

Turn real traffic into rules you control.

Mock responses, rewrite requests, and switch endpoints. Start with real traffic in DevTools and keep your frontend work moving.

Add to Chrome Add to Edge

Local-firstNo accountChrome / Edge 138+

New here? Read the quick start

ReqixInspect completed network requests, filter by type, and create rules.

4 requests

−	Name	URL	Actions
	me	https://api.example.com/users/me	Edit rule
✓	orders	https://api.example.com/orders	New rule
✓	plans	https://api.example.com/plans	New rule
	profile	https://api.example.com/profile	New rule

HeadersPayloadResponse

{
  "id": "usr_2841",
  "name": "Ada Chen",
  "role": "developer",
  "plan": "team",
  "active": true
}

Your first rule starts with a real request.Explore the DevTools panel

Made for everyday debugging

The response you need. Whenever you need it.

No mock server to set up. No application code to change. Handle the small integration problems right in the browser you already use.

Response mocking01

Make your API return what you need

Generate responses with static JSON or dynamic scripts. Set status codes and delays to test success, error, and loading states.

Explore mocks and rules

Request rewriting02

Adjust the request, keep your code

Rewrite query parameters, headers, and payloads, or redirect to another service to switch environments and reproduce issues.

See request actions

DevTools03

Create rules where requests happen

Inspect real Fetch/XHR traffic and create one or many rule drafts. Open the matching rule directly when a request needs another adjustment.

Read the DevTools guide

From install to your first rule

Fits the way you already debug.

Open the page, trigger a request, then decide what to do with it. The request details are already there.

Explore the DevTools panel

01
Open the Reqix panel
Install the extension, open browser developer tools, and select Reqix. Then refresh the page or trigger a Fetch/XHR request.
02
Pick a request and create a rule
Inspect the details and create one or many rules. New rules are disabled by default, so you can review the scope and response first.
03
Enable the rule and check the result
Enable site takeover and the relevant switches, then trigger the request again. Inspect the matched rule and processing preview, or jump back into editing.

Less back-and-forth. More progress.

For the moments that interrupt your flow.

The backend is not ready

Build the page with mock responses. Get empty lists, long text, and error messages right while you wait.

An issue is hard to reproduce

Create a rule from a captured request and response, then keep the edge case locally for repeated testing.

You need another environment

Adjust request parameters or redirect to a target service without repeatedly editing application code.

You keep pasting the same snippet

Save it as a page script and run it within a URL scope at the right point in the page lifecycle.

Local by design

Your debugging data. Your browser.

Rules and page scripts stay in extension storage. There is no account to create, no cloud sync, and no extension telemetry.

Read about privacy and permissions

No account needed: Install, configure, and use Reqix locally.
No extension telemetry: No usage analytics or uploads of your rules.
Temporary records are cleaned up: Request snapshots and hit logs older than 24 hours are removed during the next storage-maintenance run.

A handy tool for your next debugging session

Add Reqix. Get back to building.

Available for Chrome and Edge from their official extension stores.