JSONPath Finder
WebTest and extract data from JSON with JSONPath expressions in real time, with examples and match count for building and debugging complex nested queries.
[ "Go in Action", "TypeScript" ]
Related Tools
About JSONPath Finder
When you face a deeply nested JSON and want to pull out a field or filter elements by a condition, JSONPath is the most direct query tool — a syntax cousin of XPath for JSON. This tool runs JSONPath queries locally in your browser, showing matches and the hit count in real time, with built-in example expressions you can apply in one click. It supports the root symbol ($), dot child access, bracket indices and slices, the wildcard (*), recursive descent with two dots ($..price), and predicate filters in brackets such as [?(@.price<30)] where @ points to the current element. Results always come back as a JSON array, and each matched node can be shown with its full path expression for direct use in code. Working with a new API payload, you can refine the expression step by step and narrow a complex filter gradually rather than writing one long, hard-to-debug query. Nothing is uploaded, so real production JSON is safe to paste.
How to Use
- Open the JSONPath Finder tool
- Enter or paste the content to process
- Adjust the output options as needed
- Click the Run button; results appear in real time
- Copy or export the result
Use Cases
- Debug API responses — Pull a specific field out of a complex response to verify the data is as expected.
- Bulk-extract data — Use expressions like $.price to grab every field of the same name at once.
- Conditional filtering — Use [?(@.price<30)] to filter matching elements and quickly locate target data.
- Learn JSONPath — Write and see results alongside the examples to master JSONPath syntax fast.
- Design data mapping — When designing field mapping for low-code or pipelines, verify paths here first.
- Verify API contract paths — Run a JSONPath expression from your API contract against a real response to confirm the field exists at the expected path.
- Extract error details — Use $.errors[*].message to collect all user-facing error strings from a validation response in one go.
FAQ
Which JSONPath syntax is supported?
Mainstream JSONPath: $ root. child, [] index, * wildcard. recursive descent, and [?(@.field)] filter expressions.
Why is the result an array?
JSONPath may match multiple nodes, so results are always returned as an array, even a single hit is wrapped in one.
What if the expression is wrong?
An invalid expression shows "Invalid JSONPath"; fix it to re-query in real time without affecting the original JSON.
Can it handle large JSON?
Yes, queries run locally. Complex recursive queries on very large data may lag slightly — trim it with our JSON Formatter first.
Is it the same as jq?
Similar idea, different syntax. JSONPath is closer to XPath style; if you know jq, treat this as a visual in-browser alternative.
What is the difference between @ and $?
$ refers to the JSON document root, while @ refers to the element currently being evaluated (mainly used in predicate filters). Mixing them up often yields empty results or parse errors.
Why doesn't $.data[*].id match anything?
Usually the path does not match the real structure. Common causes: data is null or an object rather than an array (in that case write $.data.id); the array elements have no id field; or there are two fields named data at different depths. If you are unsure about the shape, inspect $.data first to confirm the structure, then use recursive descent $..id to grab every field named id at once and, with the live hit count and path column here, narrow down to the exact expression. Validating the expression step by step down from the $ root, rather than writing one long path blind, makes it far easier to spot which level went wrong.