JSON_PATH_FINDER_V1

JSON Path Finder

Drowning in deeply nested API responses? Paste your JSON, click any value in the tree, and the path is computed and copied to your clipboard — in either dot notation (data.users[0].profile.address.city) or JSONPath ($.data.users[0].profile.address.city).

Root var
Notation
JSON inputValid
Tree — click any value to copy its path
data
{2 keys
"data":{1 key
"users":[2
[0]:{3 keys
"id":1
"profile":{2 keys
"name":"Ada Lovelace"
"address":{2 keys
"city":"London"
"zip":"SW1A 1AA"
}
}
"tags":[2
[0]:"admin"
[1]:"author"
]
}
[1]:{3 keys
"id":2
"profile":{2 keys
"name":"Alan Turing"
"address":{2 keys
"city":"Manchester"
"zip":"M1 1AE"
}
}
"tags":[1
[0]:"mathematician"
]
}
]
}
"meta":{2 keys
"page":1
"total":2
}
}

Nothing selected yet. Click a value or key in the tree above.

Dot notation vs JSONPath

Dot notationis what you'd write in JavaScript or TypeScript: response.data.users[0].name. Keys with special characters fall back to bracket notation (response["user-id"]). JSONPath prefixes the same path with $— the convention used by tools like jq, JMESPath libraries, and Postman's test runner.

Why a configurable root name?

When you're writing code, the JSON usually lives inside a variable — response, data, or whatever fits your context. Setting that name produces a path you can paste straight into your editor.

Related JSON tools