Filters
Filter rules control which traffic shows up (or gets recorded into a session) — useful when you’re debugging one specific API and don’t want to wade through everything else your Mac happens to send.
Rule types
| Type | Matches on |
|---|---|
| Domain | Exact host, e.g. api.tonyapps.org |
| Domain wildcard | Pattern match, e.g. *.tonyapps.org |
| Path prefix | URL path starts with a string |
| Path contains | URL path contains a string |
| Method | HTTP method (GET, POST, …) |
| Content type | Response Content-Type |
| Source IP | Exact client IP (useful on a shared network) |
| Source IP prefix | Client IP range |
| Status range | Response status code range (e.g. 400–499) |
| Decode scope / exclude | Controls which traffic gets HTTPS-decoded at all |
Using filters
- Apply a filter to the live transaction list to hide non-matching rows without deleting anything.
- Attach filter rules to a session at creation time (see Session Manager) so only matching traffic gets recorded into that session in the first place — the rest is never even stored.
- Clear Filtered Traffic (⌘K) removes only what’s currently visible under the active filter; Clear All Traffic (⇧⌘K) wipes everything regardless of filter.