JSONPath Tester

JSONPath is a query language for JSON that lets you write concise expressions to select, filter, and extract data from nested JSON structures without writing loops and conditional logic. You should use JSONPath when you need to configure data extraction rules in external files, tools, or declarative specifications rather than hardcoding them in your application. Common use cases include: configuring API gateway response transformations (like AWS API Gateway mapping templates), writing data extraction rules for ETL pipelines where business analysts can write JSONPath expressions, implementing dynamic filtering in dashboard and reporting tools, selecting test data fixtures from complex JSON in automated testing, and building low-code/no-code tools where users specify data extractions without coding. Programming language libraries compile JSONPath expressions at runtime, so you get dynamic, configurable data extraction without redeployment.

Basic JSONPath expressions start with $ (root), use .key for object child access ($..store.book[0].title navigates to first book title in any store), use [n] for array indexing, use [*] for array wildcards, and use .. for recursive descent (find all title fields at any nesting level). Advanced expressions include filter predicates [@.price > 10 to filter arrays by conditions], array slicing [0:5:2 for start:end:step], union operators [0,2,4 for multiple indices], length functions to get array sizes, and bracket notation ['key'] for keys that contain special characters or spaces. For example: $.store.book[?(@.price < 10)].title selects titles of books under $10, and $..[?(@.category == fiction)] selects all objects with category field equal to fiction at any nesting level.

JSONPath is inspired by XPath (for XML) but simplified for JSON's simpler data model: JSONPath uses $ for root instead of XPath's /, uses .key instead of XPath's /key child axis, supports .. for recursive descent similar to XPath's //, and includes filter expressions similar to XPath's predicates. JSON Pointer (RFC 6901) is a much simpler standard that identifies a single specific value in a JSON document using /separated/keys/and/0/array/indexes. Unlike JSONPath which can return multiple values and filter results, JSON Pointer always returns exactly one value or fails. JSONPath is the right choice when you need to extract multiple matching values, navigate recursively, filter results, or dynamically specify queries. JSON Pointer is simpler and appropriate when you uniquely identify one specific value (like in JSON Patch operations or OpenAPI $ref references).

Yes, JSONPath libraries are available for most major programming languages. Notable implementations include: Jayway JsonPath for Java (the most feature-complete implementation, widely used via Spring Boot), jsonpath-ng and jsonpath-python for Python, JSONPath Plus for JavaScript (Node.js and browser, used by this tool), GoJSONGo for Go, rust-jsonpath for Ruby, and JSON::Path for Perl. Most implementations follow the same syntax but have subtle differences in filter expression support, recursive descent behavior, and handling of edge cases. When porting JSONPath expressions between languages, test thoroughly as filter expressions with complex conditions may behave differently. Some implementations are closer to the original Goessner specification while others follow the newer IETF RFC 9535 draft standard for JSONPath which was published in February 2024.

Common causes for empty JSONPath results include: incorrect path traversal (check each level of your path exists in the document), case sensitivity (JSON keys are case-sensitive, Name is different from name), missing recursive descent steps (use .. if you do not know the exact nesting depth), wrong array indices (JSON arrays are zero-indexed, so [0] is the first element), missing quotes in bracket notation (should be ['key'] not [key]), filter expression syntax errors (use @ not $ to reference current node in filters), and result node being null or undefined (JSONPath may skip null nodes in some implementations). Start by simplifying your expression to a basic path and verify it returns results, then progressively add complexity. Use our tester's tree view to verify the document structure matches what you expect before building complex expressions.