When one app sends information to another, it usually writes it down as JSON: a neatly labelled list that both sides can read.
When you move house, a good packing list says what’s in each box: “Kitchen: plates 12, mugs 6, kettle 1.” Anyone can read it and know exactly what’s inside.
JSON is that packing list for data. It’s a simple, labelled way of writing information as text, so one app can send it to another. The name stands for JavaScript Object Notation, but every language uses it now.
What it looks like
{ "name": "Priya", "city": "Leeds", "orders": 3 }
- each piece of information has a label in quotes
- then a colon and its value
- curly brackets wrap things that belong together
- square brackets hold lists
Where you’ll meet it
Most APIs send and receive JSON. Many apps save their settings in it. If you export data from a service, you’ll often get a .json file.
What it isn’t
It isn’t a programming language. Nothing runs. It’s just a tidy way to write things down.
Where the comparison breaks down
A packing list can be scribbled. JSON is very strict: one missing comma or bracket and the whole thing can’t be read.
How the words fit together
APIs usually speak JSON. Its shape often follows a schema. The data often ends up in a database.
JSON is just text. You can open a .json file in any text editor and read it, even if you've never coded.

When you'll hear it
“The API returns JSON.” The answer comes back as a labelled list of data.
“Send it as a JSON file.” Send the data written out in that labelled-list format.
“The JSON is malformed.” A bracket or comma is out of place, so it can't be read.
“Can we export our data in a standard format like JSON, so we're not locked in to one tool?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Pretty-print a JSON file ↗

