northdan.
Vezi pagina în română

IT Glossary

What is JSON?

JavaScript Object Notation: the simple, universal text format applications use to send each other data — the common tongue of integrations.

When two applications talk — a store requesting a shipping label, an invoicing tool submitting documents to a government e-invoicing platform, a website loading its product list — the messages almost always travel in one format: JSON, a way of writing structured data as plain text readable by machines and humans alike: key-value pairs and lists, nested as needed — {"client": "Acme Ltd", "total": 1250, "items": [...]}. It won the format wars through simplicity (its predecessor XML was heavier and noisier) and is today the lingua franca of web APIs, configuration files and many data exports. Why a businessperson benefits from recognizing it: JSON is the concrete shape a good answer takes when you ask a vendor "give us our data." At integration time, the supplier exposing a documented JSON API is the supplier who is easy to work with; at export time, data delivered as JSON (or CSV) remains reusable in any future system, whereas a PDF is a photograph of data, not data. And when a developer shows you "what the API returns," that structure with curly braces is legible to non-specialists too — a small but useful piece of transparency in technical conversations where you would otherwise have only the vendor's word.

Let’s talk about your project

Message us on WhatsApp or send an email — you talk directly to a developer.

office@northdan.com · +40 752 070 247

Why it matters for your business

The common language of integrations

Every modern system speaks JSON — connecting your applications does not stumble over conversions between exotic formats.

Data humans can read too

The key-and-value structure reads with the naked eye — debugging integrations and checking data requires no special tools.

Exports that are actually data

Information received as JSON imports anywhere, today and in five years — unlike a PDF, which is merely its photograph.

Frequently asked questions

JSON or XML — does the difference still matter?

For new systems, JSON has won almost everywhere; XML survives in established standards — including many national e-invoicing formats and older enterprise exchanges. In practice your applications will speak both where context demands, and your takeaway is simply that both are structured data — the good thing.

Can I open a JSON file without technical knowledge?

Yes — it is plain text: any editor displays it, and browsers plus free online viewers format it nicely with collapsible sections. For large files or transformations such as JSON to Excel, conversion tools abound; the data is never captive.

Why do developers ask suppliers for "JSON examples" during integrations?

A real sample response is worth ten pages of description: it shows exactly which fields exist, how they are named and how values are formatted — the integration is built and tested against it. A supplier unable to produce examples and API documentation is announcing the quality of the collaboration in advance.

Related terms

Let’s talk about your project

Message us on WhatsApp or send an email — you talk directly to a developer.

office@northdan.com · +40 752 070 247