Skip to main content

Requests Autocomplete

This functionality allows you to easily search and complete the requests you want to intercept.

tweak search

Getting search enabled#

  1. Click on the search icon in the top bar.
  2. In the browser tab, trigger the HTTP requests you want to autocomplete.
  3. Search for the request directly in the URL field - just like you would do in the DevTools/Network panel).
  4. Select a request and all the fields will be autocompleted for you.

Search for HTTP requests in a page#

  • Search by request URL, this can simply the best keyword that identifies that request you're trying to grab.
  • Search by HTTP method. If you search for GET, you will see all the GET requests available. Note: all the HTTP method keywords are case-sensitive. Sometimes it can be useful to search using the HTTP method if you have no clue how the request URL looks like, but you do know upfront its method.

You can use autocomplete in multiple tabs, tweak indexes results per browser tab session. You can always comeback later for a little search.

Using regular expressions for searching#

Yes, if you turn on the regular expression toggle, you will be able to filter results with regular expressions. Most of the times you'll be able to reach your request through the above mentioned keyword search, in any-case, for advanced use cases we make regular expressions available as wel.


You can active the regular expression filter and search for .* to get a list of all the captured requests.

Smart Filters#

You can use some labelled expression to target particular requests in the page. Below the smart filters supported:

  1. status: - use to filter by a particular HTTP response status, e.g. status:200 shows all the requests in the page with status 200.
  2. method: - use to filter by a particular HTTP method, e.g. method:POST shows all the requests in the page that have method POST (method value is case insensitive)
  3. rp:(my key word) - use to filter requests with a particular request payload (request body), e.g. rp:("operationName": "getUsers") will show only requests that have "operationName": "getUsers" in the request body.

You can combine multiple smart filters, e.g. status:404 method:get api/v1 will give you all the GET requests with status 404 to the URL endpoint that contains "api/v1".

Note about data deletion#

After deleting all the requests from the extension , remember to retrigger all the requests from the browser tab, otherwise the search results will be empty.

Was this page helpful?