JSON Path Finder
Runs in your browserOr go the other way — type $.users[0].name and jump straight to the value.
Input
Tree
Paste some JSON to start clicking around.
Resolve
Click anything in the tree.
Its path, type, and value land here, ready to copy.
ToolJar's JSONPath convention
Paths always start at the document root, written as $. Object properties use dot notation when the key is a valid identifier ($.user.name), keys that aren't valid identifiers use quoted brackets ($["first-name"]), and array elements always use a numeric index in brackets ($.users[0]). This mirrors the JSONPath dialect used by most JSON tooling, restricted to exact paths (no wildcards or filters) since every path here identifies one specific value.
Questions
- Can I use wildcards like $.users[*].name?
- Not currently — ToolJar's path finder resolves exact, single-value paths (matching what you get by clicking a node), not JSONPath query expressions with wildcards or filters.
- Why does my path say "not found"?
- Either the path syntax is invalid (shown as a parse error), or it is syntactically valid but no value exists at that location in your current document — for example, indexing past the end of an array.