📩 Hello, this is Nick from Zylosystems — hope you’re doing well this week!

In our previous newsletter, we explored what makes API docs truly developer-first—comparing the polished, hosted approach of Fern with Zylo-docs’ code-native, real-time foundation. This time, we’re turning our attention to the spec that powers most modern API docs: OpenAPI.

OpenAPI 3.2 is nearly here. With over 94% of its issues resolved, this release marks one of the most practical and forward-thinking evolutions of the spec. From flexible tag structures to official support for QUERY and multipart responses, it’s clear that the spec is catching up with how real APIs are built and shipped.

At Zylosystems, we’re not just watching the spec evolve — we’re evolving with it. Zylo-docs is already adapting to OpenAPI 3.2’s improvements, enabling richer, more expressive docs for modern teams.

📌 Topics covered in this twelfth newsletter:

• What OpenAPI 3.2 changes — and why it matters for real APIs
• How structured tags now support hierarchy, metadata, and grouping
• Why the spec now welcomes extended methods like QUERY
• How full support for multipart/* unlocks rich, streaming responses
• What Zylo-docs is doing to support these updates — today, not “eventually”

📝 Dive deeper on the blog:

👉 Why Great API Docs Matter — And How Zylo-docs Takes It Further