Trexmi
Developer Ready

JSON Path Finder

Find JSONPath-style locations for matching keys or values inside deeply nested JSON without manually tracing the structure.

Search nested JSON by key name Search scalar values as text Return every matching object or array path Handle objects and indexed arrays
INPUT Developer source value *
0 chars0 words0 lines
Paste the source value for this specific transformation. Example: Trexmi developer sample

Tool settings

Ctrl / ⌘ + Enter
JSON Path Finder result Review matching paths, depth, and copy-ready locations.
About the tool

What JSON Path Finder does

JSON Path Finder locates keys or scalar values inside nested JSON and returns their paths. It is useful when an API response is too large to trace manually or when the same property name appears at several nesting levels.

Key mode searches object property names. Value mode searches string representations of scalar values, including strings, numbers and booleans. Matching is case-insensitive and partial, so a search for user can find both user and user_id. The output uses paths such as $.account.profile.email and $.orders[0].id.

JSON Path Finder locating keys and values in nested data
Search by key or value and review every matching path.

How to use

  1. Paste valid JSON. Include the complete object or array you want to search.
  2. Enter the query. Type part or all of a property name or scalar value.
  3. Choose a mode. Select key search for property names or value search for strings, numbers and booleans.
  4. Run the finder. The result lists each unique matching path.
  5. Verify the location. Open the source at the returned path before using it in code or a mapping.
Built for the task

Why use JSON Path Finder?

Focused controls, predictable output, and a workflow designed around this exact transformation.

01

Find repeated keys

Return every matching property path instead of stopping at the first occurrence.

02

Trace deep nesting

Object names and array indexes remain visible in each path.

03

Search actual values

Value mode finds scalar values without treating nested arrays or objects as text.

04

Copy clean paths

The result is a compact list that can be checked against the original JSON.

Useful answers

Questions about JSON Path Finder

Practical details about input, output, privacy, limits, and the best way to use this tool.

01 What does JSON Path Finder do?

Find JSONPath-style locations for matching keys or values in nested JSON without manually tracing objects and arrays.

02 Does JSON Path Finder modify the original input?

No. The source remains available while the tool produces a separate result for review.

03 Can I use JSON Path Finder with real development data?

Yes, but remove secrets and confidential values first. Use representative samples and verify the output before production use.

04 Is matching exact or partial?

Matching is case-insensitive and partial. Searching for id can match keys such as id, user_id and orderId.

05 Does value mode search arrays and objects as text?

No. It compares scalar values such as strings, numbers and booleans, then returns the path of each match.

06 Is JSON Path Finder useful for debugging?

Yes. It can reduce repetitive manual inspection and make transformations easier to compare against the original source.

07 Can I paste passwords or private keys?

Avoid pasting passwords, private keys, tokens, personal records, or confidential production data into any environment you do not fully trust.

08 What should I do with invalid input?

Reduce it to the smallest failing example, correct the syntax or options, and add complexity back gradually.

Learn JSON

Read the complete JSON Guide

Learn JSON objects, arrays, value types, validation, formatting, parsing, API workflows, and common syntax errors.

  • Objects, arrays, and values
  • Validation and formatting
  • API and parsing workflows
Read guide Practical explanations and examples

Examples

Locate repeated email keys

Every matching property path is returned, including keys inside arrays.

Input
JSON: {"account":{"email":"ada@example.com"},"orders":[{"customer":{"email":"lin@example.com"}}]}
Query: email
Mode: Key name
Output
$.account.email
$.orders[0].customer.email

Find one status value

Value mode returns the location of the matching scalar rather than the parent object.

Input
JSON: {"orders":[{"id":101,"status":"paid"},{"id":102,"status":"pending"}]}
Query: pending
Mode: Value contains
Output
$.orders[1].status

Use partial key matching

Key matching is partial and case-insensitive.

Input
JSON: {"user_id":7,"orderId":19,"profile":{"IDCard":"A-42"}}
Query: id
Mode: Key name
Output
$.user_id
$.orderId
$.profile.IDCard

How key and value matching works

Key mode checks every object property name and returns all partial, case-insensitive matches. Value mode checks scalar leaf values such as strings, numbers, booleans, and null-like string representations. Nested objects and arrays are traversed, but their complete serialized contents are not searched as one block.

Choose the mode based on the question. Search keys to locate fields named email. Search values to locate records whose status contains pending.

Understanding returned paths

Object properties are appended with a dot and array elements use zero-based indexes in brackets. The first order ID may appear as $.orders[0].id. These are readable JSONPath-style locations for navigation, not a full evaluator for RFC 9535 filters, wildcards, or slices.

JSON Path Finder input and output examples

Find every email key

Input: {"account":{"email":"ada@example.com"},"orders":[{"customer":{"email":"lin@example.com"}}]}
Query: email
Mode: Key name
Output:
$.account.email
$.orders[0].customer.email

Find a status value in an array

Input: {"orders":[{"id":101,"status":"paid"},{"id":102,"status":"pending"}]}
Query: pending
Mode: Value contains
Output: $.orders[1].status

Partial and case-insensitive key search

Input: {"user_id":7,"orderId":19,"profile":{"IDCard":"A-42"}}
Query: id
Mode: Key name
Output:
$.user_id
$.orderId
$.profile.IDCard

Find boolean values

Input: {"users":[{"active":true},{"active":false}],"ready":true}
Query: true
Mode: Value contains
Output:
$.users[0].active
$.ready

Invalid input, broad queries, and verification

The source must be valid JSON. Double quotes are required around property names and string values, comments are unsupported, and trailing commas are invalid. Use JSON Validator before searching when parsing fails.

Because matching is partial, a short query such as id can intentionally find id, user_id, and orderId. Make the term more specific when the result is too broad. A returned location does not prove that the field exists in every version of an API response.

Related Trexmi tools

Inspect the complete hierarchy with JSON Viewer, check syntax with JSON Validator, or normalize compact input with JSON Formatter. When you already know the exact RFC 6901 location, resolve it with JSON Pointer Tester.

Authoritative references

See JSON specification RFC 8259 and JSONPath RFC 9535.