Pull Nested API Fields with JSONPath

Skimming a 200 KB API response for one nested id is painful. A short JSONPath does the skim for you.

How

Open /tool/jsonpath-tester, paste the JSON, enter a path such as $.data.items[0].id, and copy the match.

If it won’t parse

Fix syntax with /tool/json-validator, then pretty-print with /tool/json-formatter. Inspect JWT claims on /tool/jwt-decoder — still client-side.

Limits

Everyday $.a.b[0] paths are covered. Exotic filter expressions may need a full jq install. For most frontend debugging, the browser tool is enough.

Paths that usually work on the first try

Start at the root with a dollar sign, then dot into objects and use brackets for array indexes. If the match is empty, the path is wrong or the array is empty — pretty-print the JSON and read the actual keys before you invent a path from the docs. Keys with spaces or odd characters need different quoting than a simple name, and that is where a small tester is faster than guessing in application code. Validate first when the paste might be a fragment or an HTML error page saved as .json. A path cannot recover from invalid syntax. This is a reader, not a transformer: it will not reshape the payload into CSV. Copy the match into the ticket or the test fixture and leave the full body out of chat when it contains secrets. For a JWT, decode the token on the JWT tool instead of treating the encoded string as JSON. If the first match is a whole object, narrow the path to the field you actually need before you copy it into a ticket. Copying a customer object into chat leaks data even when the tool itself never uploaded the file. When the array index is wrong you will get a neighbor record that looks plausible, so read the id next to the value.