Skip to main content
HTTP Rules are the fastest way to change traffic without changing your app. Use them to modify headers, rewrite request or response bodies, redirect calls, inject scripts, delay traffic, or map requests to local and remote resources.

​
When To Use HTTP Rules

Use HTTP Rules when you want to:
  • modify headers, query params, bodies, or user agents
  • redirect requests between environments
  • simulate errors, delays, and edge cases
  • inject scripts or override resources during frontend testing
  • create repeatable traffic changes for demos, debugging, and QA
If your goal is to inspect live traffic first, use HTTP Interceptor. If you need hosted mock endpoints, use File Server.

​
Start With These Rule Types

Modify Headers

Add, remove, or overwrite headers for debugging and API testing.

Redirect Requests

Switch requests between environments or alternate resources instantly.

Modify Response Body

Simulate backend changes, mock responses, and reproduce edge cases.

Delay Requests

Reproduce slow networks and performance-related issues.

​
First Success Path

1

Pick One Rule Type

Start with a single change such as Modify Headers or Redirect Rule.
2

Set Match Conditions

Use URL and source conditions to target only the traffic you want to change.
3

Verify The Result

Use Test This Rule, app behavior, or your API workflow to confirm the traffic changed as expected.

​
Explore By Workflow

All Rule Types

Browse the full catalog of traffic modification capabilities.

Advanced Usage

Learn grouping, source conditions, testing, shared state, and filters.

Share Rules

Share, sync, and distribute rules with your team or workspace.

Import Existing Rules

Migrate rule configurations from other tools and extensions.

Inspect Live Traffic

Use HTTP Interceptor when you need to see requests and responses before deciding what to modify.

Hosted Mocks

Use File Server when you need reusable mock endpoints instead of in-place traffic overrides.