3 JSONPath functionality

Overview

JSONPath consists of segments separated with dots. A segment can be either a simple word like a JSON value name, or a more complex construct enclosed within square brackets [ ]. The separating dot before bracket segment is optional and can be omitted. For example:

See also: .

Supported segments

To find a matching segment ignoring its ancestry (detached segment) it must be prefixed with ‘..’ , for example $..name or $..['name'] return values of all ‘name’ properties.

Matched element names can be extracted by adding a ~ suffix to the JSONPath. It returns the name of the matched object or an index in string format of the matched array item. The output format follows the same rules as other JSONPath queries - definite path results are returned ‘as is’ and indefinite path results are returned in array. However there is not much point of extracting the name of an element matching a definite path - it’s already known.

Filter expression

Supported operands:

Supported operators:

Functions

Functions can be used at the end of JSONPath. Multiple functions can be chained if the preceding function returns value that is accepted by the following function.

Supported functions:

Incompatible input will cause the function to generate error.

Output value

JSONPaths can be divided in definite and indefinite paths. A definite path can return only null or a single match. An indefinite path can return multiple matches, basically JSONPaths with detached, multiple name/index list, array slice or expression segments. However, when a function is used the JSONPath becomes definite, as functions always output single value.

A definite path returns the object/array/value it’s referencing, while indefinite path returns an array of the matched objects/arrays/values.

Whitespace

Whitespace (space, tab characters) can be freely used in bracket notation segments and expressions, for example, $[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( ).

Strings

Examples

Input data