Add an Authorization header for one site
You want every request to one site, often an API, to carry an Authorization header or an API key, without changing your code and without sending it anywhere else.
Steps
- Install Wirelet, then open a page of the site, for example
https://api.example.com/. - Open Wirelet: click its icon in the toolbar, or press Alt+Shift+Y (Control+Shift+Y on a Mac).
- Choose “Create a profile for this site”. Your browser asks for access to this site: allow it.
- Type the header’s name,
Authorization, then its value, for exampleBearerfollowed by your token. For an API key, type the name your API expects, such asX-API-Key. - Choose “Done”, then reload the tab. The number on the Wirelet icon shows how many requests were changed.

Good to know
- The value is masked on screen; “Show value” displays it.
- “Test a URL”, in Wirelet’s settings, tells whether the profile applies to an address.
- If the requests come from a page on another site, for example your app on
localhostcalling the API, your browser needs access to both sites: the page’s and the API’s. Wirelet shows “Blocked” when one is missing. See CORS response headers in one tab. - A response that a page’s service worker serves from its cache never reaches the network: reload while bypassing the cache.
- An exported profile file holds your header values, tokens included: don’t share it.
Install Wirelet
Free · Chrome or Microsoft Edge 141 or later · English and French
Other guides
- Change the user agent in one tab onlyAnother browser or device for one tab, Client Hints included.
- Add CORS response headers in one tabTest a page that calls an API on another domain, and the limits.
- Import your ModHeader profilesFrom ModHeader’s JSON export, with a report of what changed.