Select array IDs
Input
{"users":[{"id":1},{"id":2}]}$.users[*].idExample output
[
1,
2
]JSONPath Tester
JSON & Data100% Client-SideReady
JSON
0 lines0 chars
0 B / 1.91 MB
TEXT
0 lines0 chars
0 B / 2.0 KB
Read-only
0 lines0 chars
0 B
About this tool, examples & FAQ
Query pasted JSON with deterministic root, property, array-index, quoted-property, and wildcard selectors.
Key facts
| Supported selectors | $ root, .property, [index], ['property'], and [*] |
|---|---|
| Code evaluation | None; script and filter expressions are unsupported |
| Processing | Local Web Worker; JSON is not uploaded |
| Maximum input | 2.0 MB |
How to use
- Paste a valid JSON document in the first editor.
- Enter an expression beginning with $, such as $.users[*].id, in the second editor.
- Run the query and inspect the JSON array of matched values and its match count.
- Refine the path or copy the result into another JSON tool.
Example
Edge cases
Focused syntax
Recursive descent, filters, scripts, and unions are intentionally unsupported.
No matches
A valid expression that selects nothing returns an empty JSON array rather than an error.
Quoted properties
Use bracket notation such as $['property-name'] when a property cannot be expressed with dot notation.
How it works
- Parses the JSON document before processing the path.
- Converts the path into property, index, and wildcard selector tokens.
- Traverses values iteratively without eval, functions, network access, or script expressions.
Related workflows
Frequently asked questions
Are filter expressions supported?
No. This first version supports common deterministic selectors only.
Why did I get an empty array?
The expression was valid but none of its selectors matched the supplied JSON structure.
Does this implement every RFC 9535 selector?
No. It intentionally implements a safe common subset and clearly rejects recursive descent, filters, unions, slices, and scripts.
References
- RFC 9535 — JSONPath — JSONPath terminology and selector model