ToolsAtlas
Simple online tools for developers, networking, text and conversions.

Developer Tools

JSON Path Finder Examples

Review practical JSON Path Finder examples so you can understand expected input, output, and common patterns faster.

Why examples matter for JSON Path Finder

Use this JSON Path Finder to search a JSON object or array for matching key names and return their paths with values. It is useful for large API responses, webhook debugging, field discovery, payload analysis, and quickly locating where a specific key appears inside nested JSON. You can provide the JSON and a search term in JSON format or with a separator block.

Example pages are especially useful for developer tools because they show what good input looks like, what kind of output to expect, and how the tool behaves in common scenarios.

JSON Path Finder examples

Find one nested key by name

Input

{"json":{"user":{"id":7,"profile":{"email":"a@example.com"}}},"query":"email"}

Output

{
  "query": "email",
  "matchCount": 1,
  "matches": [
    {
      "path": "$.user.profile.email",
      "value": "a@example.com"
    }
  ]
}

Useful when you know the field name but not where it appears in the structure.

Find repeated id keys in nested JSON

Input

{"json":{"user":{"id":7},"orders":[{"id":101},{"id":102}]},"query":"id"}

Output

{
  "query": "id",
  "matchCount": 3,
  "matches": [
    {
      "path": "$.orders[0].id",
      "value": 101
    },
    {
      "path": "$.orders[1].id",
      "value": 102
    },
    {
      "path": "$.user.id",
      "value": 7
    }
  ]
}

Useful when the same key appears in several different parts of a payload.

How to use these examples

  1. Provide input as JSON with json and query fields, or separate the JSON and search term with ---
  2. Click Run Tool to search the structure
  3. Review the list of matching paths and values
  4. Use the result to inspect the target field or continue with another JSON tool
  5. If needed, use JSON Key Extractor to review the full structure

Common mistakes in sample input

Only raw JSON is pasted without a query

Fix: Use JSON with json and query fields, or separate the JSON and query with ---.

The search term is too broad

Fix: Use a more specific key name to reduce noisy matches.

The JSON input is invalid

Fix: Format or validate the payload before running the search.

The user expects full JSONPath query language support

Fix: This tool searches key names and returns matching paths. It is not a full JSONPath evaluator.

No matches are returned because the wrong key name is searched

Fix: Use JSON Key Extractor first to inspect the exact path names available.

Next steps

After reviewing these examples, run the live tool with your own input. If your task involves a follow-up step, the related page can help you move to the next tool in the workflow.

Run the main tool

Open the main JSON Path Finder page and test your own real input.

Open JSON Path Finder