The typical jq session starts blind: you guess a filter, run it, read the error, and adjust. jsonblocks removes the guessing by showing the document structure first, with the exact path of every value one click away.
The explore-then-query workflow
- 01
Paste the document into the path finder or the block visualizer.
- 02
Click the value you want and copy its path, for example $.data[0].email.
- 03
Convert to jq by swapping the root: jq '.data[0].email' data.json.
- 04
Extend from a working base: add pipes, selects, and maps with confidence.
# copied path: $.data[0].email
# jq filter: .data[0].email
jq '.data[0].email' response.json
jq '[.data[].email]' response.json
What each tool does best
Path syntax translation
Viewer paths and jq filters differ only at the root: drop the $ and the rest is identical for simple keys. $.store.book[0].title becomes .store.book[0].title. The path finder shows both forms side by side so the translation is never a guess.