Input
Tree
Resolve
JSON Path
$Type
objectValue
{"id":"ord_8f3c2a","status":"shipped","createdAt":"2026-01-14T09:32:00Z","total":128.5,"currency":"USD","customer":{"name":"Priya Nair","email":"[email protected]","verified":true,"address":{"street":"221B Baker Street","city":"London","country":"UK","postalCode":"NW1 6XE"}},"items":[{"sku":"SKU-001","name":"Mechanical Keyboard","quantity":1,"price":89.99},{"sku":"SKU-014","name":"USB-C Cable","quantity":2,"price":9.5},{"sku":"SKU-027","name":"Wrist Rest","quantity":1,"price":19.51}],"tags":["electronics","peripherals"],"discountCode":null,"metadata":{"source":"web","campaign":null,"referrer":"https://example.com/deals"}}ToolJar's JSONPath convention
Paths always start at the document root, written as $. Object properties use dot notation when the key is a valid identifier ($.user.name), keys that aren't valid identifiers use quoted brackets ($["first-name"]), and array elements always use a numeric index in brackets ($.users[0]). This mirrors the JSONPath dialect used by most JSON tooling, restricted to exact paths (no wildcards or filters) since every path here identifies one specific value.
Questions
Can I use wildcards like $.users[*].name?
Not currently. ToolJar's path finder resolves exact, single-value paths (matching what you get by clicking a node), not JSONPath query expressions with wildcards or filters.
Why does my path say "not found"?
Either the path syntax is invalid (shown as a parse error), or it is syntactically valid but no value exists at that location in your current document, for example indexing past the end of an array.