←  All terms
J
APIs & Integrations

JSON

JSON is a text-based format for structured data commonly used to exchange information between applications and APIs.

JSON is a text-based format for structured data commonly used to exchange information between applications and APIs. Strong implementations use explicit data contracts, secure authentication, error handling, and observable operations. The concept is closely related to REST API and API.

Read more

REST API

API

JSON-LD

Data Integration

FAQ

JSON

Is JSON-LD the same as JSON?
No, JSON-LD is a use of JSON that adds semantics. Every JSON-LD document is valid JSON but adds keywords such as @context and @type, which tie data to defined vocabularies. An ordinary API response counts as JSON-LD only if that structure has been implemented deliberately.
What typical mistakes occur with JSON interfaces?
Typical failures are missing schema validation, unannounced changes to field names, and inconsistent error responses. A field that suddenly returns a number instead of a string often breaks an integration only in production. A documented data contract with versioning and automated tests exposes such changes before they reach users.
Which data types can JSON represent?
JSON supports objects, arrays, strings, numbers, booleans, and null. Dates, binary data, and comments have no native form and are usually encoded as text by convention, for example in ISO 8601 notation. Sender and receiver have to agree on that convention, otherwise silent misinterpretations creep in.
Why is JSON used more often than XML for APIs?
JSON is more compact, easier for people to read, and maps naturally onto JavaScript objects. That made it the default format for web APIs. XML remains a fit when schemas, namespaces, or document-like structures dominate. The choice of format should follow the requirements of the interface rather than fashion.