JSONPath Query Tool - Online JSON Data Extraction

1. Run a query

Paths that “work” on happy JSON often fail on sparse production payloads.

1. Paste or load a JSON document that mirrors production shape (redact secrets first).
2. Enter a JSONPath expression — start with $ for the root, then descend with dots or brackets.
3. Inspect the match list; tighten the path until only the intended nodes remain, then copy results.

2. Expressions that pull weight

Recursive descent (..) finds keys at unknown depth — powerful and easy to over-match. Filters on arrays (scripts or comparisons, depending on the dialect this UI implements) narrow lists of objects. Prefer explicit paths in CI assertions; reserve recursive descent for exploration.

• Start explicit ($ .store.book[0].author) before going recursive.
• Count matches — surprise extras mean the path is too loose.
• Normalize JSON (format/sort) when comparing path results across environments.

3. Dialect and portability

JSONPath has multiple dialects (Goessner-style, RFC 9535 efforts, library-specific extensions). An expression that works here may need adjustment in another language binding.

4. Failure modes

Empty results are usually path mistakes, not empty products. Prove the node exists with a shallower path, then deepen.

• Trailing commas or comments in “JSON” — parse fails before any path runs; strip with a formatter first.
• Assuming objects are arrays — filters silently return empty.
• Matching string vs number — "10" and 10 are different nodes.

5. Security and privacy

Documents may contain tokens or PII. Evaluation is local, but do not paste production dumps into shared calls. Paths themselves can encode business structure — treat saved expressions as mildly sensitive in public gists.

6. Related tools

Use the JSONPath generator when you want help drafting a path from a clicked node. Format or diff JSON first when payloads are noisy. Schema validators catch shape drift that brittle paths will miss. Export matched arrays to CSV when analysts need a table.

7.

Document dialect assumptions next to the path in code review so future editors do not “fix” it into another library’s syntax.

3. The same path is revalidated in the production language library before merge.

8. From exploration to assertions

Exploration mode favors short recursive paths. Assertion mode should freeze an explicit path and an expected match count in tests. When product adds an optional nested object, decide whether assertions should ignore it or require it — silent extras from recursive descent cause flaky tests. If matches include huge subtrees, project to the fields you need before pasting into tickets — huge JSON in chat is how secrets leak. Recursive descent over multi-megabyte JSON can stall the tab. Narrow with an explicit prefix path first. Prefer multiple precise queries over one maximal recursive exploration in shared workshops.

• Freeze explicit paths and expected counts in CI.
• Avoid pasting huge match subtrees into chat tickets.

9. Operator note

Capabilities for “jsonpath-query” follow the controls visible on the page today. Keep a minimal success sample and a minimal failure sample next to your runbook so regressions are obvious after browser or dependency upgrades. When handing results to someone else, write one line naming source file, options used, and what the tool explicitly does not guarantee. Prefer repeating a known-good path over inventing options that do not exist on screen.