Recently, I had dinner with a few tech friends, and the conversation drifted to the new data element policy. One guy who works on backend at an e-commerce company said something that stuck with me: "The API data running through our company's systems is like a subway station during rush hour—it looks like everything's moving, but it's actually a total mess."
Crude but accurate. After the new policy took effect, data is officially being managed as a production factor. What does that mean? It means all that data you used to casually stuff into databases, log files, or even some colleague's desktop now needs a proper identity. API data in particular—many enterprises have never managed it properly.
What is API data? Simply put, it's what gets passed between systems. For example, after you place an order, the order system needs to tell the inventory system to deduct stock, tell the payment system to collect money, and tell the logistics system to prepare for shipment. Every time data is passed, a bunch of JSON-formatted data is generated. It looks pretty neat—curly braces nested inside curly braces, key-value pairs neatly arranged. But the problem is, too many people write APIs, everyone has a different style, and over time it all falls apart.
The most absurd case I've seen: at one company, the user ID in the JSON returned by the user API was sometimes called "uid," sometimes "userId," and sometimes "user_id." Frontend developers had to check the docs every time they integrated, then test after reading the docs, only to find the docs didn't match the actual response. Not to mention those structures nested seven or eight levels deep—open one up and your eyes glaze over.
That's where JSON formatting tools come in. Don't underestimate this feature. Many people think it's just expanding a compressed single-line JSON into multi-line with indentation—what's the technical depth? But anyone who's actually done the work knows how much a good formatting tool can save you. It can clarify messy hierarchical relationships, letting you see at a glance which field is in which object, which array contains which properties. Especially when debugging APIs, before and after formatting are two completely different worlds.
The new policy requires data to be manageable, traceable, and assessable. If you can't even see clearly what your API data looks like, how can you manage it? How can you trace it? So the first step is making data readable. That's exactly what JSON formatting does—turning something machines can read but humans struggle with into something humans can easily understand. It's not some profound technology, but it's the starting point of all data governance work.
My e-commerce friend later introduced a rule at his company: all API documentation must include formatted JSON examples, and before submitting code, everyone must use a formatting tool to check the response structure. At first everyone found it troublesome, but later they discovered integration testing time was cut in half, and no one complained anymore. See, sometimes managing data well isn't that complicated—it starts with making good use of a formatting tool.