# Filter JSON Response

You can quickly filter the JSON Response with the following approach:

### 1. Filter on JSON Previewer

* **⌘F** to trigger the Filter
* Support Regex
* Support Jump Next

![](/files/-MIxxuqk-fVjjHSX9dcr)

### 2. JSONPath

Proxyman supports [JSONPath](https://github.com/json-path/JsonPath#path-examples) for quickly querying the data in JSON Document.

![](/files/-MfzvapgK9JWsYTJn6dt)

Please check out JSONPath documentation.

{% content-ref url="/pages/-MfzfoPRgCYnSYnY6JsG" %}
[JSONPath](/~/revisions/CTFzuwrlmsieJaiDVRDD/basic-features/jsonpaths.md)
{% endcontent-ref %}

###  3. KeyPaths

* Support Key Paths filter on JSON Tree View mode
* Search specifically the children keys 

Syntax example:

* **posts\[1].maker\[2]**: Go from Root -> Get item at index 1 of the Posts array -> Get the index 3 items of Makers array and filter out
* **users.name**: Get the name value of the "users" dictionary 

![](/files/-MIxy5sNhUXUbfvyiijX)

### 4. All Keys or All Values

* Show all nodes that the key or value contains the search text

![](/files/-MIxzB4KkDq13VJqL13z)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.proxyman.com/~/revisions/CTFzuwrlmsieJaiDVRDD/basic-features/filter-json-response.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.