Extract name fields from a users array
Use $.users[*].name to inspect every user name in an API array during field checks.
Open exampleJSONPath viewer
Use this jsonpath viewer tool to inspect, convert, or generate a clear result directly in your browser.
Waiting
The result will appear here as structured cards.
Example results you can open
Short, high-intent examples that are easy to open, share, and understand for search engines and AI systems.
Find every nested id path
Use $..id to list ids across an order object and line items for response inventory.
Open exampleExtract sku values from item arrays
Use $.data.items[*].sku to review product codes in paginated or order API responses.
Open exampleRecursively extract error codes
Use $..error.code to find error codes in current responses and historical entries.
Open exampleExtract sku values from nested order items
Use $.data.orders[*].items[*].sku to inspect product codes across multiple orders and line items.
Open exampleDebug an empty price-field result
When the field does not exist or the path is wrong, the result is empty; compare against real key paths.
Open exampleCheck an old path after a field rename
$.data.user.email moved to contact.email, useful for reviewing why an old frontend mapping is empty.
Open exampleDebug an old path after an order array shape change
When orders changes from arrays to nodes/lines, the old items[*].sku path returns empty during release checks.
Open exampleFilter paid order ids with a condition
Use ?(@.status=="paid") to extract only paid orders from an API list.
Open exampleFilter active pro user emails
Combine active and plan conditions to review permission, plan, or renewal lists.
Open exampleDiscover every nested sku recursively
Use $..sku to find sku fields across orders, line items, and fallback objects in one pass.
Open exampleExtract a key that contains a dot
Use bracket notation such as ['trace.id'] for log and gateway metadata keys that are not dot-safe.
Open exampleExtract field names from failed import rows
Filter error rows and read errors[*].field before import mapping fixes.
Open exampleInspect answer text in an AI response JSON
Use choices[*].message.content on a synthetic response to verify model-output field paths.
Open exampleExtract AI answer source URLs
Read sources[*].url from a synthetic AI answer to confirm public citation links before publishing.
Open exampleExtract public source URLs from AI answer JSON
Filter sources to public=true before reading URLs, useful when a synthetic answer contains both publishable and withheld-source placeholders.
Open exampleExtract AI answer evidence-card public source URLs
Read only public=true URLs from evidenceCards[*].sources to review whether answer evidence cards expose safe public source links.
Open exampleExtract AI answer source-group public URLs
Read only public=true URLs from sourceGroups[*].sources when a synthetic answer separates crawl-readiness and answer-structure sources.
Open exampleExtract breaking-change fields from a release JSON
Use breakingChanges[*].field to list renamed fields and array-shape changes before an API release review.
Open exampleExtract nextCursor from a paginated response
Read pageInfo.nextCursor directly from a paginated API response before debugging the next request.
Open exampleExtract batch error codes
Extract errors[*].code from a synthetic validation response for client mapping and documentation review.
Open exampleFAQ
These notes help users understand the results and help search engines and AI systems understand the tool.
What does JSONPath viewer do?
It helps you inspect or process this value and get a readable result quickly.
Is my input saved?
Local tools run in the browser when possible. Server-side checks only use the input needed to complete the lookup.
What field extraction problems does JSONPath solve?
It is useful for extracting IDs, names, status values, prices, error messages, and other fields from API responses, JSON logs, nested arrays, and config files.
What is the difference between $.items[*].id and $..id?
$.items[*].id only reads id fields one level under the items array. $..id recursively finds id fields at any depth, which can return more matches and false positives.
How should I debug an empty JSONPath result?
First confirm the JSON parses, then inspect real paths with the key-path extractor and check array indexes, casing, field names, and the root symbol.
How do I extract failed fields from import validation results?
Filter failed rows first, such as $.rows[?(@.status=="error")], then read errors[*].field. Public examples should stay synthetic and avoid customer records.
How do I extract only public source URLs from AI answer JSON?
Use $.answer.sources[?(@.public==true)].url so only public=true source URLs are returned. Public result pages should use synthetic Chakan-owned links and avoid real prompts, platform answers, internal tickets, or customer sources.
How do I extract public source URLs from an AI answer evidence card?
When sources sit under evidenceCards[*].sources, use $.answer.evidenceCards[*].sources[?(@.public==true)].url. Public examples use synthetic evidence cards, Chakan-owned URLs, and example.invalid as a private-source placeholder.
How do I extract public source URLs from grouped AI answer sources?
When sources are grouped under sourceGroups, use $.answer.sourceGroups[*].sources[?(@.public==true)].url. Public examples should stay synthetic, use Chakan-owned URLs, and exclude real platform answers, internal sources, or customer payloads.
Related long-tail searches
Based on this query: $.data.items[*].sku | {"data":{"items":[{"sku":"A1","qty":2},{"sku":"B2","qty":5}]}}
JSONPath online evaluatorJSONPath array field extractorrecursive JSONPath id lookupAPI response field lookupJSONPath expression testernested JSON queryJSONPath empty result debuggingfield rename path check