Feature Overview

reqable provides a complete frontend debugging workflow centered on request monitoring and API mocking.

The main interface is an in-page sidebar that can be opened with a shortcut or context menu. Request monitoring and mocking are also available in Chrome DevTools under the Mock Panel tab.

---

API mocking

Mocking is reqable's core capability, covering request capture, rule matching, request rewriting, and response replacement.

Request monitoring

• Capture all XHR and Fetch traffic from the current page in real time.
• Display the URL, method, status code, and duration.
• Search by URL, path, method, request body, response body, and other fields.
• Match with contains, does not contain, equals, does not equal, or regular expression.
• Inspect complete Query, Headers, Body, and response data.

Mock rules

• One-click creation: double-click a monitored request or use its plus button.
• Groups: isolate rules for different projects or scenarios.
• Enable/disable: control rules individually or in batches.
• Ordered priority: rules are tested from top to bottom; the first match wins.

Match strategies

Strategy	Description
Precise	Requires the complete URL and request-body fingerprint to match.
Smart	Tries a precise match first, then falls back to endpoint matching.
Endpoint	Matches only the URL path and ignores the query and body.
Custom	Combines a URL mode, method, and optional body comparison.

Custom URL modes include exact, contains, regex, and endpoint matching.

Mock capabilities

Each rule can enable the following capabilities independently:

• Replace response with custom data.
• Simulate an error by rewriting the response status.
• Simulate a timeout (XHR uses timeout=1; Fetch is marked as timed out).
• Rewrite the request body.
• Rewrite request headers.
• Rewrite query parameters.
• Delay the response by a specified number of milliseconds.

Response editor

• Monaco Editor provides JSON highlighting and completion.
• Normal mode edits JSON or text directly; advanced mode executes a JavaScript response function.
• AI refinement updates a response from natural-language instructions.

AI features

• Configure an OpenAI-, Anthropic-, or Gemini-compatible provider and API key.
• Generate mock responses in bulk from YApi schemas.
• Refine a response from the mock details view.
• Review streamed output and a diff before accepting changes.

Import

• Import OpenAPI/Swagger, Postman Collection, HAR, and cURL data.
• Import OpenAPI files exported by platforms such as Apifox.
• Connect to a self-hosted YApi service and browse its interfaces.
• For YApi imports, choose AI generation or YApi mock import.
• AI generation uses the YApi schema; direct import reuses data already maintained in YApi and does not require AI configuration.
• AI-generated rules retain the YApi context for later refinement.

Request replay

• Export all currently monitored requests as mocks for initial-page replay.
• Add all monitored requests directly to the mock list.
• Record only requests created during a focused interaction.
• Recorded requests receive a REC marker.
• Import the exported file in another page or browser.

Mock import and export

• Export the current group or every group as a JSON file.
• Import a reqable JSON file into a selected group.
• Back up or migrate all extension data from Settings → Data management.

Cache recovery

• Restore a page from locally cached successful responses when an API temporarily fails.
• Configure the applicable domains and cache limits.

See Cache Recovery.

Preferences

• Follow the browser language or explicitly select Chinese or English.
• Follow the system theme or explicitly select light or dark mode.
• Configure the YApi service URL instead of relying on a built-in company endpoint.
• Store settings, mock rules, and UI preferences in extension-local storage.