JSONPath Tester

About JSONPath tester

Paste a JSON document, type a JSONPath expression, and see every value the expression selects together with the normalized path to each one. It is built for people debugging API responses, writing queries for config tools or test assertions, and checking a filter before it goes into code. The evaluator implements a practical subset of the syntax rather than every dialect.

How to use it

1. Paste your JSON into the JSON document box, or press Load sample to start with the bookstore document.
2. Type an expression into the JSONPath expression field. It has to start with $, which stands for the root of the document.
3. Or click one of the Try an example buttons, such as Cheap books or First two, to see working syntax.
4. Read the Matches card: the badge shows the count, and each result lists its normalized path above its value.
5. Use Copy all values or Download JSON to take the matches away as a JSON array, or copy one value with the button beside it.

Filtering the sample bookstore

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

2 matches
$.store.book[0].title  ->  "Sayings of the Century"
$.store.book[2].title  ->  "Moby Dick"

When to use it

• Working out the right path to a deeply nested field in a REST response before hard-coding it in a script.
• Testing a price or date filter against sample data before adding it to a monitoring rule.
• Showing a teammate how recursive descent with two dots differs from a plain child lookup by comparing match counts.
• Finding out why an expression returns nothing by looking at the exact paths that do match.

Questions about JSONPath tester

Which JSONPath syntax is supported?

The root $, dot and bracket child access, array indexes including negative ones, wildcards, recursive descent, unions like [0,2], slices like [1:4] or [::2], and filters using ==, !=, <, <=, >, >=, && and ||. Script expressions beyond those comparisons are not evaluated.

What does a filter such as [?(@.isbn)] do?

A filter with no operator is an existence test. It keeps the array items that have an isbn property, so in the sample document only the third book is returned.

Why does the tool complain about JSON before it looks at my path?

The document is parsed first with the browser's strict JSON parser. Trailing commas, single quotes and comments are rejected, and the message repeats the parser's own description of where it gave up.

Can I count from the end of an array?

Yes. A negative index counts backward, so $.store.book[-1].title returns the last title, and the match is reported under its real position, $.store.book[2].title.

Will results match other JSONPath libraries?

For the listed syntax, yes. Libraries historically disagreed on edge cases such as filter functions and duplicate handling, so re-test anything exotic in the library you deploy with.

Related tools

• JSON validator & beautifierValidate JSON content and make it looks good.
• SQL formatter/beautifierFormat & beautify your SQL code with ease.
• URL parserParse details from any URLs.
• JSON viewerExplore and search JSON data in a collapsible tree view.
• JSON to CSV converterConvert a JSON array into CSV with nested flattening, a custom delimiter and an optional header row.
• CSV to JSON converterConvert CSV text into JSON with delimiter auto-detection, header-row and type-coercion toggles.