JSON Path Finder Guide: How to Query JSON Data with JSONPath

$ — Root Object

The root of the JSON document. All expressions start here.

$ → the entire JSON document

.property or ['property'] — Child Operator

Access a direct child property of an object.

$.store.bicycle.color → "red"

[*] — Wildcard

Selects all elements of an array or all properties of an object.

$.store.book[*].title → ["1984", "Dune", "Neuromancer"]

.. — Recursive Descent

Search through all descendants at any depth. The most powerful JSONPath operator.

$..price → [9.99, 14.99, 12.99, 199]

[?(…)] — Filter Expression

Filters array elements using boolean expressions. Supports comparison operators, logical operators, and existential checks.

$.store.book[?(@.price < 14)].title -> ["1984", "Neuromancer"]

$.store.book[?(@.price >= 10 && @.price <= 15)].title -> ["Dune", "Neuromancer"]

$..book[?(@.author)] -> books that have an author field

[start:end:step] — Array Slice

Extract a sub-array by index range, similar to JavaScript slice.

$.store.book[0:2].title → ["1984", "Dune"] $.store.book[::-1].title → ["Neuromancer", "Dune", "1984"]

[0,2] — Union

Select multiple specific indices from an array.

$.store.book[0,2].title → ["1984", "Neuromancer"]

Find all titles in a nested structure

$..title

Recursive descent finds title at any depth — ideal for unknown or deeply nested schemas.

Get the last element of an array

$.store.book[-1:]

Negative indices count from the end, just like Python or JavaScript.

Filter with negation

$.store.book[?(@.price < 10)]

Find books priced under $10. Supports <, <=, >, >=, ==, != operators.

Check for existence of a field

$.store.book[?(@.isbn)]

Selects only objects that have an isbn field — great for filtering sparse data.

Kubernetes-style JSONPath

{.items[*].metadata.name}

Kubernetes uses a curly-brace variant. Our JSON Path Finder supports this syntax too.

1. Using single quotes in filters

JSONPath filters require double quotes around string literals.$[?(@.status == 'active')] will fail in most implementations.

2. Forgetting the root symbol ($)

Every JSONPath expression must start with $. Writing .store.book instead of$.store.book will return empty results.

3. Confusing dot and bracket notation

Dot notation only works for simple identifiers.$.store.0.name is invalid — use$.store[0].name for numeric array indices.

4. Assuming regex support

Standard JSONPath (RFC 9535) does not support regular expressions. Only specific libraries like Jayway add =~ operator. For portability, use exact string matches or wildcards.

5. Using unsupported features in your target library

Not all JSONPath libraries support every operator. For example, some older JavaScript libraries do not support [::-1] slice syntax. Always test your expression with the exact library version you deploy in production.