JSONPath Syntax Cheatsheet

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from JSONPath Syntax Cheatsheet

JSONPath Syntax Cheatsheet summarizes path expressions for locating values inside JSON objects and arrays. A JSONPath expression describes where to look in a document, starting from a root context and navigating properties or array elements. Implementations differ in advanced operators and result conventions, so the expression should be checked with the parser used in your application. A cheatsheet works best as a memory aid while you practice a concrete task. Read the command or syntax together with its arguments, placeholders, and surrounding context. Similar-looking options can have very different meanings, and an example written for one platform or version may need adjustment elsewhere. Keep the reference beside a small test case, use read-only examples first when possible, and check the relevant help output before applying an unfamiliar command to valuable files or a running service.

Guide updated October 13, 2026

How to use this tool

1. Identify the operation you want to perform and find the matching section of the reference. Read the whole example before copying any part of it.
2. Choose a path pattern matching the data shape and evaluate it against a small document in the intended JSONPath implementation.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Try the adapted example on a small test case, compare the result with the explanation, and save the command with a note about the context in which it works.

SEE IT IN PRACTICE

A worked example

JSON {"users":[{"name":"Ada"}]} with path $.users[0].name

A result identifying the value Ada

The path starts at the root, selects users, chooses array element zero, and then reads its name property.

Paths depend on the input shape

A path beginning at the root can navigate named properties and array indices, but it cannot infer that a response wrapper changed or that a collection sometimes appears as a single object. Compare the expression with the actual JSON structure, not just a field name you expect to exist somewhere. Test zero, one, and multiple matching records. A path that returns the first item successfully may still hide a requirement to process every item in a collection.

Implementation and result conventions matter

Advanced filters and functions are not identical across every JSONPath implementation. The return value may also be a list of matches even when only one item matched, which affects downstream code. Use the same library and options as the consuming application when validating an expression. Record both the path and a sample document in tests. If a query returns nothing, inspect property case, array nesting, and the context before changing the expression into an overly broad recursive search.

When this tool is useful

• Locate a nested field in an API response
• Review an array selection expression
• Understand root and property navigation in JSONPath

Tips for a better result

• Check no-match behavior, multiple matches, array indexing, and the exact returned value shape before integrating the expression.
• Replace example paths, identifiers, and names deliberately. Copying a reference command unchanged can target a different file, branch, service, or environment from the one you intended.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions