View My JSON
Skip to main content
Blog

The best way to read JSON from APIs and config files

A practical order for reading unfamiliar JSON: confirm it parses, learn its shape, pick a view, check types and nulls, and format last. With examples.

Most of the time you read JSON because something is wrong. A request failed, a feature flag is not taking effect, a number on a dashboard looks off. You are not trying to admire the document, you are looking for the one field that explains the problem. People who are quick at this tend to follow the same order of operations without thinking about it. This post writes that order down, with examples from the kinds of documents you actually open at work.

Sources and further reading

Try the JSON workspace