JSONPath Tester

JSON Input

          

JSON Tools

Test JSONPath expressions online

Use this JSONPath tester when you need to extract a specific value from a nested API response, config file, or sample payload. Paste valid JSON, enter a JSONPath expression, then review the matched values and the concrete paths returned by the query.

search

Query nested JSON

Use root, dot notation, bracket notation, array indexes, wildcards, and recursive descent to reach deeply nested values.

filter_alt

Test simple filters

Evaluate filters such as @.price < 10 or @.active == true against arrays and objects.

content_copy

Copy path results

The output includes match count, matched values, and paths, so you can copy or download the result for debugging notes.

What is JSONPath?

JSONPath is a query syntax for selecting data from JSON, similar in spirit to using selectors for nested structures. The root symbol $ represents the whole JSON document. From there, dot notation such as $.order.id, bracket notation such as $["order"]["id"], array indexes, wildcards, recursive descent, and simple filters can select the values you need without writing custom traversal code.

How to use this JSONPath tester

  1. Paste valid JSON into the JSON input panel, or load the sample data.
  2. Type a JSONPath expression in the path field, starting with $.
  3. Select Test, or press Enter while the path field is focused.
  4. Review the output object for match count, values, and concrete paths.
  5. Copy or download the result when you want to use the matched data in a test, script, ticket, or API note.

Common JSONPath use cases

API payload querying

Pull IDs, prices, flags, or names from nested API responses before writing application code.

Test assertions

Work out the exact path for Postman tests, integration checks, fixtures, and monitoring rules.

Nested data debugging

Use recursive descent or wildcards when the value exists at different depths or inside repeated records.

Config inspection

Query large JSON configuration files to confirm a field exists without manually expanding every branch.

JSONPath example

Input JSON and query

{
  "orders": [
    { "id": "ord_1", "total": 24, "paid": true },
    { "id": "ord_2", "total": 9, "paid": false }
  ]
}

$.orders[?(@.paid == true)].id

Result

{
  "matches": 1,
  "values": [
    "ord_1"
  ],
  "paths": [
    "$.orders[0].id"
  ]
}

This query filters the orders array to paid orders, then returns the matching id values and their source paths.

JSONPath Tester FAQ

What does this JSONPath Tester do?

It evaluates a JSONPath expression against valid JSON and returns the matched values plus the concrete paths where those values were found.

Is my JSON uploaded or stored?

No. JSONPath evaluation runs in your browser and pasted JSON is not submitted to devbruh.dev for querying. Still, avoid pasting production secrets, credentials, private tokens or sensitive customer data into any online tool unless you are comfortable with the environment you are using.

Which JSONPath syntax is supported?

This tester supports the root symbol $, dot notation, bracket notation, array indexes, wildcards, recursive descent, and simple filters such as @.price < 10 or @.active == true.

Does this tester support slices, unions or full RFC 9535 JSONPath?

No. It covers the common query syntax used for quick inspection, but array slices, unions, functions and the full RFC 9535 feature set are not supported on this page.

What is the difference between JSONPath and a JSON tree viewer?

JSONPath is for writing an expression that selects matching values. A JSON tree viewer is better when you want to browse the whole structure visually before deciding which path to query.

What should I do if a JSONPath query returns no matches?

Check that the JSON is valid, confirm the key names and array indexes in the JSON Tree Viewer, and make sure the expression starts with $.

Learn more about JSONPath

JSONPath implementations do not all support the same syntax, so it helps to check both the standard and the evaluator you plan to use in code. These references are useful when you need exact behavior.