Rules & matching
Be specific about the requests you want to change.
Sign in to the TrafficDeck console and create your first rule.
Choose an action
Use redirect, block, request/response header changes, query parameter changes or a static mock response. Available runtime behavior depends on the rule type and supported browser scope.
Choose a rule in the ledger on the left. Inspect its settings on the right.
Actual product UI · Demonstration data, not a live sessionNarrow the match
Match URLs, hosts or paths using equals, contains, wildcard or regex. Add method and resource-type conditions where appropriate. Test with a narrow URL before expanding a rule.
A practical API mock example
To test an empty state or a failed order request, start with one controlled endpoint and a static response. Keep the matcher narrow, verify the response in your test page, then inspect the matched rule before adapting it to another endpoint.
Preview before saving
Use the product preview to evaluate your matching conditions. A preview checks the configuration; trigger a real request to verify its browser effect.
Keep the limits in mind
Arbitrary live response-body rewriting, request-body modification and a system-wide desktop proxy are outside the approved MVP.