How to extract configuration values from json with jsonpath
- Step 1Paste the configuration JSON — Paste your app.config.json, appsettings.json, or infrastructure config. Files can be deeply nested — the JSONPath expression navigates any depth.
- Step 2Write an extraction expression — Use $..connectionString to find all connection strings at any depth, $..['enabled'] to find all enabled flags, or $.environments[?(@.name == 'production')].endpoint to find the production endpoint.
- Step 3Verify the extracted values — Review the matched values to confirm they are non-empty, correctly formatted, and match expectations (e.g. production URLs start with https, port numbers are integers).
- Step 4Use in documentation or deployment scripts — Copy the extracted values for use in deployment documentation, config validation scripts, or infrastructure-as-code variable files. Use the same JSONPath in CI scripts for automated config validation.
Frequently asked questions
How do I extract all keys at a specific nesting depth?+
Use the wildcard at the desired depth: $.services.* extracts all direct children of services, and $.services.*.endpoints[*].url extracts all endpoint URLs across all services. The recursive descent operator $.. finds a key at any depth: $..url finds all url keys everywhere in the config.
Can I check if a required key exists and is non-empty?+
Use a filter expression: $.services[?(@.apiKey && @.apiKey != '')].name to find all services that have a non-empty apiKey. This is useful for validating that required secrets have been injected before a deployment.
Are configuration values — including connection strings — transmitted to JAD Apps?+
No. JSONPath evaluation runs entirely in your browser. Configuration values, connection strings, and any sensitive settings are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.