1
JSONPath/XPath access to Environment Variables
Source: Kong/insomnia#3731 · opened by @js-mode
[Feature Request] Would like to ability to use specific workspace environment variables in the JSONPath queries. Currently we querying API with specific order numbers and am getting back very large JSON response for customer. Would like to filter the JSONPath filter using the variable that is set on the GET API request. This would also be valuable for those that are constantly running the same JSONPath queries for that specific environment - for example if you are always running $..[?(@.customer == '50')] to filter out the information for just that environment (per call) so that you can have set environment variables you can use for JSON responses that are returned on an environment basis. The data may change, which is why it would be nice to parse out specific environment variables that you can throw into the JSONPath query section. The history is very useful, but if the query is long enough, it is a lot easier to use specific variables (such as CustomerID…
No pledges yet. Be the first to back this.
Comments
Similar requests
Use JMESPath instead of or in addition to JSONPath (JSONPath sucks.)
15 votes · 0 comments
[Feature Request] Add XPath 2.0 support for XML response filtering
4 votes · 0 comments
Redesign the environment variables
1 vote · 0 comments
Indicate when response filter (JSONPath/XPath) input is invalid/non-existent
1 vote · 0 comments
Turn on / off the JSONPath expression
4 votes · 0 comments
No comments yet.