JSONPath data query
JSONPath locates a value inside a JSON document with a path expression, the same way XPath does for XML, but without one single standard: every implementation decides filter and negative-index details on its own, and that is where a query that works in one library silently fails in another.
`[*]` is the array wildcard: it iterates every element of the `book` array (4 books) and pulls the `author` field from each, without needing the numeric index.
`@.price` refers to the price of the book being evaluated inside the filter; of the 4 books, only 2 cost less than 10 (8.95 and 8.99), so the query returns exactly those 2 titles.
The same concrete path is written differently in each output dialect (JSONPath, dot notation, JS accessor, Python and jq); jq uses a dot with no `$`, Python brackets and quotes every key, JS mixes dot and bracket depending on whether the name is a valid identifier.
Yes. You write the query and it is evaluated against the JSON you pasted, returning the list of matched values and the concrete path of each one. The engine covers the root, child access by dot and bracket, indexes (including negative ones), slices with a step, the wildcard, recursive descent, unions, and filters with comparison, existence and logical operators. It all runs in the browser, with the document never sent to a server.
It searches for a field at any depth in the document, not just one level below the current point; `$..price` finds every `price`, whether it sits inside a book, inside a product nested 5 levels down, or loose at the root.
Yes, RFC 9535, but it arrived decades after Stefano Goessner original 2007 proposal; many libraries in use today still follow pre-RFC conventions (like parenthesized `?()` filters), which explains small syntax differences between tools.
They serve the same purpose (locating a node inside a data tree) but for different formats: XPath navigates XML, including attributes and text nodes, which JSON has none of; JSONPath navigates only JSON object, array and scalar-value structure.
A syntactically valid path that matches no node in the document (a misspelled field name, for example) returns an empty result list, not an error; an error only appears when the expression syntax itself is malformed.
4 matched values
"Nigel Rees""Evelyn Waugh""Herman Melville""J. R. R. Tolkien"$objobj.JSON stays in your browser. Files opened here are never uploaded, and neither queries nor values reach analytics.