JSON (JavaScript Object Notation) is a lightweight, text-based data format used for storing and exchanging data. It is easy for humans to read and write, and simple for machines to parse and generate. JSON is language-independent but widely supported across programming languages, making it a standard for data interchange in modern web development and APIs for the following reasons. * **Human-Readable and Simple** - JSON is structured and easy to understand, making it developer-friendly for both reading and debugging. * **Lightweight** - Its compact format reduces bandwidth usage, improving performance for data transfer in web and mobile applications. * **Interoperability** - JSON is supported by virtually all programming languages and platforms, ensuring seamless integration between systems. * **Easy to Parse** - Most languages have built-in functions or libraries (e.g., JSON.parse() in JavaScript) for parsing JSON data, simplifying processing and manipulation. * **Flexible Data Structures** - JSON supports key-value pairs, arrays, and nested objects, allowing representation of complex data structures. * **Compatibility with JavaScript** - Since JSON is based on JavaScript syntax, it integrates naturally with JavaScript applications, including front-end frameworks like React, Angular, and Vue.js. * **Standardization** - JSON is defined by RFC 8259 and ECMA-404, ensuring consistent usage across systems and applications. JSON is the preferred format for data exchange due to its simplicity, flexibility, and compatibility with modern programming languages and frameworks. Mobile applications were the initial driver of adoption for JSON, but it has spread much wider to the desktop, server, and every other aspect of API operations.
JSON
JSON (JavaScript Object Notation), standardized as RFC 8259 and ECMA-404, is a lightweight, text-based format for representing structured data as key-value pairs, arrays, and nested objects. It grew out of JavaScript syntax but is language-independent, and it is now the default payload format for the overwhelming majority of web APIs.
- Human-readable text - Easy to read, write, and debug by hand, unlike binary serialization formats.
- Simple type model - Objects, arrays, strings, numbers, booleans, and null cover most data needs.
- Universal parsing - Nearly every language ships built-in support for encoding and decoding JSON.
- Schema-describable - Paired with JSON Schema to add validation, contracts, and documentation.
In API operations JSON is the request and response body carried as application/json — the shape OpenAPI documents, JSON Schema validates, and JSONPath queries. Its ubiquity is also its governance challenge: because anything can emit JSON, teams lean on schema and linting to keep payloads consistent across an estate. For AI agents consuming APIs, predictable, well-described JSON is what makes a response reliably machine-parseable instead of something to scrape.
Referenced on the API Evangelist blog
Where this standard shows up across sixteen years of my writing at apievangelist.com — how it fits into API design, governance, and the agentic turn.
Editing JSON Schema in YAML
2025-03-31
The Basic Building Blocks API Governance
2025-03-14
Schema Work is the Most Stabilizing API Work
2025-02-25
What is JSON Schema?
2025-01-07
