Request headers · Chrome 120+

Modify request headers.
Keep testing in control.

Test APIs in Chrome with exact-host header rules, environment profiles, and automatic expiry. Narrow rules to an API path or fetch/XHR calls, with settings stored in your Chrome profile.

Built for API and web-environment testing
  • Local settings
  • Exact-host site access
  • No telemetry
ReqKit popup with an API-scoped staging header, an enabled debug header, and a paused trace header
Built for focused testing

Useful controls, without the configuration maze.

Exact-host rules and environment profiles keep every change scoped, visible, and reversible.

Exact-host headers

Create, pause, edit, and remove request headers only for HTTPS hosts where you grant ReqKit site access through Chrome.

Environment profiles

Keep staging, QA, and other rule sets separate, then select the one environment that should apply.

Automatic expiry

Apply a profile for one hour, eight hours, the browser session, or until you explicitly turn it off.

Privacy-conscious by default

Settings stay in the current Chrome profile. ReqKit has no analytics, remote code, account system, or developer server.

Request headers

Control the current host from one focused popup.

Create, pause, edit, and remove request headers for an exact HTTPS hostname, optionally limited to API paths or fetch/XHR requests.

  • Optional path-prefix and fetch/XHR-only matching
  • Current-host and all-rule views stay one click apart
  • Sensitive-looking values masked in the popup
  • Review and revoke site access without deleting rules
ReqKit showing exact-host request-header rules
Rule manager

Keep every environment organized.

Review rules by profile and hostname, switch how long a profile runs, and see exactly what is active before continuing your test.

  • Compact profile tabs with rule counts
  • Rules grouped by exact HTTPS hostname
  • One-hour, eight-hour, session, or manual expiry
ReqKit Rule Manager showing profiles, timing, and request-header rules
Profiles

Separate rule sets without losing context.

Create, rename, duplicate, or delete profiles in a dedicated view while the active setup remains visible behind it.

  • Active profile clearly highlighted
  • Rule counts visible before switching context
  • Duplicated profiles start with every copied rule paused
ReqKit profile duplication dialog explaining that copied rules start paused
A short workflow

Configure, apply, continue.

1

Open ReqKit

The popup identifies the current hostname and shows the rules that affect it.

2

Choose what applies

Select a profile and activation lifetime in the rule manager, then turn on only the rules you need.

3

Keep testing

Chrome applies rules marked On to matching exact-host requests and stops them automatically when configured.

Privacy you can inspect

No hidden data pipeline.

ReqKit's source, permissions, storage behavior, and complete privacy policy are public. Header values may still be logged by destinations or intermediaries, so use only authorized systems and test data.

Read the privacy policy

Start your next API test with ReqKit.

Install in Chrome 120 or later. No account is needed. ReqKit asks for site access when you create or resume a rule for an HTTPS host.

  1. 1
    Add ReqKit to ChromeOpen the store listing and choose Add to Chrome.
  2. 2
    Open it on your test siteReview the privacy notice, then add an exact-host rule.
  3. 3
    Choose what applies and for how longUse profiles and the auto-off timer in the rule manager.
Developing or reviewing the source?

Clone the GitHub repository, open chrome://extensions, enable Developer mode, choose Load unpacked, and select the extension directory.

Solve a testing task.

Practical guides with example headers, matching rules, and checks you can repeat.

Before you install

Does ReqKit modify response headers?

ReqKit manages request headers for exact HTTPS hosts. It does not edit response headers, inspect response bodies, or bypass CORS.

Does it have access to every website?

ReqKit requests site access on demand for the exact host a rule needs. Chrome also lets you manage extension access; review any exact or broader grants in the rule manager's Site access overview.

Where are my rules stored?

In the current Chrome profile, without a ReqKit account, analytics, or developer server. Enabled header values reach matching destinations and may appear in their logs. Read the privacy policy for details.