A lighter Requestly alternative for header rules

Requestly is a capable platform. If what you use it for is changing headers and redirecting URLs, Headerbench does that with no account, fewer permissions and a flat price for extras.

What Requestly does better

• A full API client for building and sending requests.
• Team workspaces with shared rules.
• Script and CSS injection into pages.
• Mocks with custom status codes and delays, and GraphQL mocking.

If you need those, stay with Requestly.

When Headerbench fits better

• You want header rules, redirects and blocks without signing in to a web app. Headerbench has no account.
• You want an extension that asks for four permissions and no site access at install. Requestly’s manifest requests 11, including webRequest, proxy and browsingData.
• You want a personal price: Headerbench Pro is $36 a year or $79 once. Requestly’s team plans start at $10 per user per month, billed annually.

Recreate a header rule in Headerbench

1. Install Headerbench and choose Start with a blank profile.
2. Name the profile after the environment, for example Staging API, and tag it staging.
3. On Request headers, add Authorization set to Bearer eyJhbGciOi… and X-Api-Version set to 2.
4. On Filters, add the domain api.staging.example.com and pick the request type fetch/XHR.
5. For a URL redirect, open Redirects & blocks and send https://staging.example.com/app.js to http://localhost:5173/app.js.
6. Open your app, turn the profile on in the popup and allow access to the staging domain and your app’s page when Chrome asks.
7. Use Test a URL with https://api.staging.example.com/v2/users to check both headers apply.

Headerbench can’t read Requestly exports yet; it imports ModHeader and Headerbench files.