Search
The search box at the top filters the request list as you type. Ctrl L puts the cursor in it.
How terms match
Section titled “How terms match”- Separate terms with spaces. A request is listed only when every term is found in it.
- Case doesn’t matter.
- A method matches only a whole term:
postfindsPOSTrequests,posdoesn’t. - URLs, servers, headers and bodies match part of the text:
cartfinds/v2/cart/items.
| Search | Lists |
|---|---|
api.example.com |
Requests to that host |
post cart |
POST requests with cart in the URL |
bearer |
Requests carrying that word, once headers are in scope |
Where it looks
Section titled “Where it looks”The menu at the right end of the search box sets the scope. Tick any of:
- URL and method (on by default)
- Request headers
- Request body
- Response headers
- Response body
The menu’s label sums up the scope: URL, URL, headers, Everywhere when all five are ticked, Nowhere when none are.
Headers are searched as name: value lines. Bodies are searched with their Content-Encoding removed, so a gzipped JSON response is searched as JSON. The label reads Searching… while headers and bodies are being read.
Other ways to narrow the list
Section titled “Other ways to narrow the list”- The quick filters above the list’s columns pick requests by protocol, content type and status class.
- Choose hosts, folders or resources in Structure to list only what’s under them.
- Filter hosts above the tree narrows the tree itself.
- The filter button above the list hides ERR rows and passed-through connections.
- The star button beside it lists only your favourites.
- Following a connection lists only the requests that went over it.
A request with an open draft in the composer stays listed whatever the search, so you can see its response when you send it.