Developer Tools
JSONPath Tester
Query JSON with JSONPath expressions like $.store.book[*].author or $..price and see every match with its exact path.
How to use
- 1Paste your JSON and type a JSONPath expression.
- 2Matches and their paths appear instantly.
How it's calculated
Supported: $ root, .key and ['key'], [n] and [-n] indexes, [a,b] unions, [start:end] slices, * wildcards and .. recursive descent.
Frequently asked questions
What does $..price mean?
The .. operator searches at every depth, so $..price returns every 'price' value anywhere in the document.
Are filter expressions supported?
Not yet — [?(@.price < 10)] style filters are planned. Use wildcards and then scan the results for now.
How do I select a key with spaces or dots?
Use bracket notation with quotes: $['first name'] or $.data['a.b'].
Worked example: JSONPath Tester
Given {"store":{"book":[{"author":"A","price":8},{"author":"B","price":12}],"bike":{"price":20}}}, the expression $.store.book[*].author returns 2 matches: $.store.book[0].author → "A" and $.store.book[1].author → "B". Switch to $..price on the same document and the recursive-descent operator finds all 3 prices in the document regardless of depth — the two book prices and the bike's — because .. doesn't care where price appears in the tree, only that the key exists somewhere below the current point.
What's actually supported, and what isn't yet
This implementation covers the JSONPath operators people reach for constantly: dot and bracket key access ($.key or $['key']), numeric and negative array indexes ($.a[-1] for the last element), slices ($.a[1:3]), comma-separated unions ($.a[0,2]), wildcards (*) and recursive descent (..). It deliberately doesn't support filter expressions like [?(@.price < 10)] — those require evaluating a boolean condition per element, which is a meaningfully bigger feature. The practical workaround today is a wildcard plus scanning the results, or combining this with the JSON Diff or JSON Formatter tools if you need to isolate matching records by value.
Why this beats grep-ing a JSON file
Searching a large API response or log file with grep for a key name finds raw text matches with no sense of structure — it can't tell you whether 'price' at line 40 is nested inside 'book' or 'bike', and it breaks the moment the JSON is minified onto one line. JSONPath instead walks the actual parsed structure, so $..price reliably finds every occurrence regardless of formatting or nesting depth, and each result comes back labeled with its exact path ($.store.bike.price), which is often the detail you actually needed — not just the value, but where it lives in the document.
Negative indexes and slices clamp instead of erroring
Against {"a":[10,20,30,40]}, the expression $.a[-2:] returns the last two elements — $.a[2] → 30 and $.a[3] → 40 — because a negative slice boundary is converted to length + boundary before the range is walked, the same convention Python uses for negative slicing. Ask for a range that runs past either end of the array (say $.a[1:99]) and it simply clamps to the array's actual bounds rather than throwing an out-of-range error, which makes slices forgiving to experiment with when you're not sure exactly how long an array is.
Unions let you pick specific indexes without writing out a slice
$.a[0,2] against the same array returns exactly $.a[0] → 10 and $.a[2] → 30 — the comma-separated union selector is for cherry-picking specific, possibly non-contiguous positions, which a slice can't express since a slice is always a contiguous run. Each requested index is resolved independently (including negative ones, so $.a[0,-1] grabs the first and last elements), and any index that falls outside the array's bounds is silently skipped rather than producing an error — useful when you're testing a path expression against a few different sample documents that don't all have arrays of the same length.
Related tools
- Regex Tester
Test JavaScript regular expressions live — see every match highlighted, capture groups, named groups and match positions.
- API Tester (Online REST Client)
Send HTTP requests from your browser — any method, query params, headers, JSON or form body, bearer/basic/API-key auth — and inspect status, timing, headers and pretty-printed JSON. Export as cURL, JavaScript or Python.
- CORS Tester
Test whether an API allows cross-origin requests from the browser — any method, headers and credentials. See if a preflight was needed, what failed, and get the server config to fix it.
- Webhook Tester (Request Bin)
Get a unique URL that captures every HTTP request sent to it — method, path, query, headers and body — to debug webhooks from Stripe, GitHub, Shopify, Zapier and more.
- Fake Test Data Generator (JSON / CSV)
Generate realistic fake people — names, emails, phones, addresses, companies — as JSON or CSV for testing and demos.
- Structured Data (JSON-LD) Validator
Paste JSON-LD (or a page's HTML) to check it's valid JSON, uses schema.org correctly and includes the key properties for common rich result types.