The History of JSON: From JavaScript to the Lingua Franca of APIs

In 2001 Douglas Crockford distilled a minimal data format from JavaScript object literals. Two decades later it became the common language of internet APIs. Here is the story of JSON's birth, standardization and rise.

The History of JSON: From JavaScript to the Lingua Franca of APIs

From a convenient extraction to a standard

In 2001, programmer Douglas Crockford noticed that JavaScript's object literal syntax was itself a great way to describe data: key-value pairs, arrays and nesting — readable and parseable by nature. He distilled it into an independent data format named JSON (JavaScript Object Notation) and published the spec at json.org in 2002.

The context was Web 2.0: pages needed to fetch data asynchronously (AJAX). Compared with XML, JSON was lighter, closer to native JavaScript, and nearly free to parse — it spread quickly on the browser side.

The road to standardization

2006 — RFC 4627, the first official specification;
2013 — standardized as ECMA-404; RFC 7159 revised it the same year;
2017 — RFC 8259 became the current internet standard (aligned with ECMA-404).

Why JSON won

JSON's grammar is minimal — only six kinds of values:

Objects { "key": value }
Arrays [ value, ... ]
Strings, numbers, booleans and null

No comments, no extra markup. Humans read it easily, machines parse it easily, and nearly every language ships a built-in parser. That made it the de facto standard for REST APIs — today the vast majority of web interfaces exchange JSON.

Common misconceptions

JSON vs JavaScript: JSON is an independent format, different from JS object literals (e.g., keys must be double-quoted, strings must use double quotes);
JSON has no comments: a design choice that keeps the format clean and shareable across languages.

In summary

JSON's story is simple: take a simple idea to its extreme, and meet the moment's need exactly. Today it is the lingua franca of data exchange, from web frontends to servers to databases.