About the JSONPath Tester
JSONPath is the query language for JSON that tools such as Postman, Kubernetes, AWS CLI and many API gateways use to pick values out of a response. This tester evaluates an expression against the document you paste and shows the results as a JSON array, updating as you type, with the count in the status. It supports the constructs you will actually meet: dot and bracket notation, the wildcard *, recursive descent .., array indexes and slices, unions, and filters like [?(@.price < 15)] with comparison and regex operators.
The document is validated first, so a malformed JSON reports a line and column rather than an empty result. Because JSONPath implementations differ in the corners, the behaviour here follows the common Goessner semantics used by most libraries; if a tool you target behaves differently for an edge case, its documentation wins.
To list every path in a document so you can copy the right one, use the JSON Path Finder. The XML equivalent is the XPath Tester.
How to use
- Paste JSON on the left, or use the sample.
- Type a JSONPath expression in the toolbar.
- Read the matching values; the count is in the status.
Common questions
- What filter syntax is supported?
- Comparisons such as ==, !=, <, <=, >, >= against a literal, a regex test with =~ /pattern/, and existence checks like [?(@.tags)].
- How do I get all values of a key anywhere?
- Use recursive descent: $..price returns every price at any depth.
- Why does my expression return nothing?
- Check the key names and that arrays are indexed with square brackets. The JSON Path Finder lists every valid path in your document.
- Is this the same as jq?
- No. jq is a separate language with a similar goal. Many simple selections translate directly by dropping the leading $.