Webhook HMAC Signer
Sign and verify GitHub, Stripe, and Slack webhook signatures locally.
OpenWrite a path, see what it matches, and learn where JSONPath and JMESPath part ways.
Drop API responses or config files into the editor.
Try JSONPath ($.a.b) or JMESPath-style (a.b[*]) expressions.
Review both result panels to see how each path dialect resolves.
Export the selected nodes for scripts, tests, or docs.
You are writing an alert rule that needs the price of every item in an API response, and the monitoring tool expects a JSONPath expression. Guessing and redeploying is slow; testing the expression against a real response here takes a few seconds per attempt.
Paste a JSON document and type a path. The supported JSONPath subset covers dot and bracket child access, quoted keys, array indexes including negative ones, wildcards, recursive descent with .., slices like [0:3] or [::2], and unions like [0,2] or ['name','price']. Results update live in two panels. The first shows the JSONPath node list, which is always an array. The second evaluates the same expression with JMESPath-style rules, returning a single value for a plain path and an array only when the expression projects with a wildcard, slice or union. Every match is also listed with its concrete path, and clickable chips suggest paths taken from your own document.
Filter expressions such as [?(@.price > 10)] are intentionally unsupported, so nothing in an expression is ever executed. Select the parent array with a wildcard and apply the condition in your target library instead. Recursive descent has no JMESPath equivalent, so the second panel reports an error for it, which is a useful reminder when porting paths between tools. If the document will not parse, the JSON validator points at the bad line, and the JSON viewer helps you explore a large structure before writing a path.
The document and every expression you try stay in this browser tab.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
JSONPath always returns a list of matched nodes. JMESPath returns the value itself for a plain path and only builds an array when the expression projects, for example with a wildcard over an array.
Use bracket notation with quotes around the key, either single or double. Dot notation stops at characters such as spaces and dots, so a key like order id needs the quoted form.
The JSONPath panel, as a formatted JSON array of the matched values. To keep the JMESPath-style result, select and copy it from its own panel.