RAML and API Blueprint: where are they now?

The once-contentious API design landscape has largely settled in favor of the OpenAPI format, originally known as Swagger, which emerged victorious in the API specification battles of the early 2010s. OpenAPI's widespread adoption is attributed to its open-source ecosystem, tooling agnosticism, and support from major industry players through the OpenAPI Initiative. While RAML and API Blueprint still exist, their adoption rates lag significantly behind, with OpenAPI being the most widely used due to its ability to both design and document APIs effectively. Companies like MuleSoft and Apiary continue to support their respective formats alongside OpenAPI, though the latter's dominance is reinforced by its rich ecosystem, community backing, and inclusion in platforms like Postman. The OpenAPI Initiative remains open to community involvement to shape its future, emphasizing collaboration over competition to avoid reigniting past specification battles.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.