About the JSON Path Finder
When a value is buried six levels deep, the hard part is writing the path to it correctly. This tool walks the whole document and prints one JSONPath expression per node, root first, in document order. Object keys use dot notation when they are valid identifiers and bracket notation otherwise; arrays always use a numeric index in brackets. Switch to bracket notation for every key if you are targeting a library that requires it.
The paths follow the JSONPath convention with $ as the root, which is what jq (with minor syntax differences), the JSONPath libraries in most languages, Postman tests and many API gateways accept. Paste a path into the JSONPath Tester to run it against the same document.
Large documents produce a long list; use the browser search in the output pane, or filter by copying the output into a text editor.
How to use
- Paste JSON on the left.
- Find the path you need in the list on the right, using the notation your tool expects.
- Copy the line and use it in your query or code.
Common questions
- Is the path format compatible with jq?
- Mostly. jq uses
.a.b[0]without the leading$, so remove it. Keys with special characters need quotes in jq as in bracket notation here. - Can it find the path of a specific value?
- It lists all paths; search the output for the value or key name to find the one you want.
- What is the difference between dot and bracket notation?
- They address the same nodes. Bracket notation works for every key, including those with spaces or dashes; dot notation is shorter for ordinary identifiers.