This extract is used to read data from JSON files and Web Services. A JSONFile or Rest connection type is needed.
The extract definition uses JSONPath language, which is a standard query language for selecting nodes from a JSON document. You can find more information on JSONPath at http://goessner.net/articles/JsonPath/.
Under Settings, you have the option to use caching for none (default), memory, or disk. See Caching in Extracts for more information.
Settings
| Connection | JSONFile or REST connection. Only connections with HTTP modes GET and POST are possible for JSON extracts using REST connections. Note: during a data preview of the extract, the POST request is executed, which may provoke undesired changes on the service endpoint. |
| JsonPath Loop Expression | Dropdown list of reasonable JSONPath expressions that specify the root or anchor element to loop through in the JSON source file. You can define as many JSONPath expressions as you want, each of which defines one column of the extract output.
Expressions can also be entered manually. |
| Export data fields/JsonPath expression | Dropdown list of expressions that define a column of the extract output or the xpath from the Json loop expression. For each column, a name and a default value can be defined. All space, multiple space, or null values will be mapped to this default value. |
If caching is activated, the complete output of the extract is temporarily stored during the first call of the extract, using an internal H2 database. Subsequent calls of the extract read directly from the cache without connecting to the underlying source system of the extract. If the extract or the underlying connection contain variables, a separate cache is build for different values of these variables.
See Caching in Extracts for more information.
Updated June 5, 2023