1 item
Add or override HTTP request headers on outgoing requests, with an optional URL filter per rule. No tracking, no data collection. Add or override HTTP request headers on outgoing requests — a lightweight, privacy-first tool for developers. FEATURES • Add custom request headers (e.g. Authorization, X-API-Key, custom debug headers) • Optional URL filter per rule — apply a header to specific sites only, or leave it blank to apply everywhere • One-click global toggle to enable or disable all rules at once • Rules persist locally and survive browser restarts HOW IT WORKS HeaderNinja is built on Chrome's declarativeNetRequest API (Manifest V3) — the modern, secure way to modify network requests without the performance and privacy costs of the older webRequest blocking API. Your rules are stored locally in the browser and applied directly by Chrome's network layer. PRIVACY • No tracking, no analytics, no telemetry • No data ever leaves your browser • No remote code — everything runs from the files in this package • Only two permissions requested: declarativeNetRequest (to apply your header rules) and storage (to save your rules locally) WHO IT'S FOR Developers, QA engineers, and API testers who need to inject or override headers — auth tokens, feature-flag headers, custom user-agents — without spinning up a proxy or editing requests by hand. Licensed under MPL-2.0.
Aug 29, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.