Finding Paths in Nested JSON
When working with deeply nested API responses, it's easy to lose track of the exact path to a value — is it response.data.user.address.city or response.user.data.address.city? Our tree viewer shows the full path to any selected node, so you can build correct accessor expressions without trial and error.
This is especially useful when writing code to process complex JSON: GraphQL responses with nested fragments, Kubernetes API outputs, AWS CloudFormation templates, or Stripe event objects. Navigate the tree visually, identify the value you need, and get the exact path to use in your code.
Knowing the precise path also helps when writing jq filters, JSONPath queries, or kubectl jsonpath expressions. Instead of guessing the syntax, navigate here first and copy the path structure directly.
Tips
- Dot notation for objects:
response.data.user. Bracket notation for arrays:items[0].name. - In JavaScript, optional chaining (
response?.data?.user?.name) prevents crashes on undefined intermediate keys. - For
jq: paths look like.data.users[0].email— the tree view helps you build these correctly. - In Python, nested dict access:
data["users"][0]["email"]— matches the JSON path exactly.