Evaluate JSONPath expressions

Q: What does $..id match?

Every id key anywhere in the document, at any depth, in document order. It is the quickest way to answer where does this field appear.

Q: Why does my expression return nothing?

Most often a case mismatch in a key name, or a missing array index where the path crosses a list. Try the same path one segment shorter to see where it stops matching.

Runs locally

Query a document with $.path syntax and see the matches instantly.

Expression

Supports dot paths, [index], [*] wildcards and .. recursive descent.

Document

{
  "store": {
    "book": [
      { "title": "Sayings of the Century", "author": "Nigel Rees", "price": 8.95 },
      { "title": "Moby Dick", "author": "Herman Melville", "price": 8.99 },
      { "title": "The Lord of the Rings", "author": "J. R. R. Tolkien", "price": 22.99 }
    ],
    "bicycle": { "color": "red", "price": 19.95 }
  }
}

Matches

4 matches

[

8.95,

8.99,

22.99,

19.95

]

About the JSONPath evaluator

How it works in 4 steps · 4 common use cases · 3 questions answered

How it works

1.Paste the document on the left.
2.Type a JSONPath expression, starting from $ for the root.
3.Matches are listed as you type, so a wrong path shows up immediately rather than at runtime.
4.Copy the matched values, or the expression once it is right.

Common use cases

•Writing an extraction rule for a monitoring or ETL tool and checking it against a real payload
•Pulling every id out of a nested response without writing a script
•Testing a config selector before committing it
•Learning what .. recursive descent actually matches in your document

FAQ

Which JSONPath syntax is supported?

Dot notation, bracketed keys and indexes, [*] wildcards and .. recursive descent — the subset that covers most extraction rules. Filter expressions such as [?(@.price<10)] are not evaluated.

What does $..id match?