About JSONPath Query — Detailed Guide
The JSONPath Query tool evaluates standard JSONPath expressions (such as `$.store.book[*].author` or filter predicates like `$[?(@.price < 10)]`) against arbitrary nested JSON documents in real time.
Features live syntax evaluation, path match count, formatted result previews, and error diagnostics—enabling backend engineers and QA testers to fine-tune API assertions without writing temporary test scripts.
Key Features & Capabilities
- Supports standard JSONPath syntax (root `$`, current `@`, wildcard `*`, recursive `..`)
- Rich filter expression predicates with comparison and boolean operators
- Real-time calculation showing matched node count and beautified output
- 100% client-side execution keeping confidential JSON payloads private
How to Use
- 1
Paste your JSON payload into the source editor.
- 2
Type a valid JSONPath expression into the query bar (e.g., `$.items[*].id`).
- 3
Inspect the matched node array and copy the extracted results to clipboard.
Common Use Cases
- → Testing extraction assertions for Postman, JMeter, or Newman API test suites
- → Extracting deeply nested attributes from cloud logs and OpenAPI specifications
- → Quickly filtering specific subsets of records from massive mock datasets
Related Tools
JSON Formatter
Format, validate, prettify, and minify JSON data with syntax highlighting and customizable indentation.
Markdown Preview
Live render Markdown with GFM, math equations, code highlighting, and export to HTML.
YAML JSON Converter
Convert data between YAML and JSON formats with syntax validation and error reporting.
SQL Formatter
Format and beautify SQL queries with support for multiple database dialects and indent styles.
XML Formatter
Format, minify, and validate XML documents with syntax highlighting and tree view.
CSS Formatter
Format, beautify, and minify CSS, SCSS, and Less stylesheets.
Frequently Asked Questions & Privacy
What is the difference between `$` and `@` in JSONPath?
`$` represents the root JSON document from which query starts, whereas `@` represents the current item being evaluated inside filter expressions.
How do I query all items recursively regardless of depth?
Use the recursive descent operator `..`. For example, `$..price` extracts all `price` properties throughout the entire document hierarchy.