What is JSONPath?

JSONPath is XPath for JSON—a query language that lets you extract values from JSON documents using path expressions. Instead of writing loops to find data, you write a single expression like $.users[*].email to get all user emails.

Syntax Quick Reference

Working Example

Consider this API response:

{
  "store": {
    "name": "TechMart",
    "products": [
      { "id": 1, "name": "Laptop", "price": 999, "inStock": true },
      { "id": 2, "name": "Mouse", "price": 29, "inStock": true },
      { "id": 3, "name": "Keyboard", "price": 79, "inStock": false },
      { "id": 4, "name": "Monitor", "price": 299, "inStock": true }
    ],
    "location": {
      "city": "San Francisco",
      "country": "USA"
    }
  }
}

Example Queries

Filter Expressions

Filters ([?()]) let you select elements that match a condition. Use @ to reference the current element:

• [?(@.price > 100)] — Price greater than 100
• [?(@.price <= 50)] — Price 50 or less
• [?(@.inStock == true)] — In stock items
• [?(@.name)] — Has a name property
• [?(@.tags[*] == "sale")] — Has "sale" in tags array

Real-World Use Cases

Extract All Emails from API Response

$..email

Finds every email field anywhere in the document—useful when you don't know the exact structure.

Get Failed Items from a Batch Response

$.results[?(@.status == "failed")]

Filters to only the items that failed processing.

Find Products in a Price Range

$.products[?(@.price >= 10 && @.price <= 50)]

Combines multiple conditions with &&.

Get Specific Fields from Nested Arrays

$.orders[*].items[*].sku

Extracts SKUs from all items in all orders.

Pro Tips

• 💡 Start with $ and build up — Test $.storebefore trying $.store.products[?(@.price>100)].name
• 💡 Use .. when you're not sure of the path —$..id finds all IDs regardless of nesting depth
• 💡 Filter returns an array — Even if one item matches, you get [item] not item
• 💡 Dot notation vs bracket notation —$.store.name equals $['store']['name']. Use brackets for special characters: $['my-field']

JSONPath vs Alternatives

Related Tools

• JSON Validator — Validate and format JSON
• JSON Diff — Compare two JSON documents
• JSON Schema Validator — Validate against a schema

Common Mistakes & Pro Tips

• Dot vs bracket notation — $.store.book and $['store']['book'] are equivalent. Use bracket notation with quotes when a key contains spaces, dots, or special characters, for example $['user.name'] or $['first name'], since dot notation would misparse those. The root is always $.
• Wildcards and array indices — Use [*] to select all elements or members at a level, and numeric indices like [0] for a specific element. Many implementations support slices such as [0:2] and negative indices like [-1] for the last item. Combine them: $.store.book[*].author selects every author.
• Recursive descent with .. — The .. operator searches all levels, so $..author finds every author key anywhere in the document regardless of depth. It is powerful but broad; it can match in unexpected branches, so scope it (for example $.store..price) when you only want part of the tree.
• Filter expressions use @ — Filters like [?(@.price < 10)] keep elements where the predicate holds, with @ referring to the current element. You can test existence ([?(@.isbn)]) and combine conditions with && and ||. Quote string comparisons carefully, e.g. [?(@.category == 'fiction')].
• Implementations differ — JSONPath was never a single formal standard until RFC 9535, so older libraries differ on slices, filter syntax, regex matches, and whether results are values or paths. If an expression behaves unexpectedly, it may be an implementation quirk rather than a mistake in your query.