It’s been incredible to see the API revolution over the last couple of years, how APIs have become the defacto standard for all of software. It is no longer just a tool for hardcore developers, but one that anyone tech-savvy can use. And with this maturity, the number of API description languages as ways to explain the behavior of APIs has also exploded, creating a need for broad support across multiple languages when adopting best-of-breed technologies.
Today, we are excited to announce the introduction of OpenAPI Specification 3.0 support across the full API lifecycle with Anypoint Platform. We embarked on this journey last year when we introduced design and discovery support, and are excited to be closing it out in the new year. This adds to our growing library of supported languages, joining RAML and OAS 2.0 (aka Swagger) to give Anypoint Platform users maximum flexibility when deciding which API standard is best suited for them.
A new definition of agile
With the proliferation of API description languages and the adoption of newer technologies like GraphQL, AsyncAPI, and gRPC — it’s become even easier for developers to swap and pivot to new technologies. And finding the right technology for the job, not being chained to one tech stack, has been a cornerstone of agile development for years. Now, as organizations grow, they are discovering that they cannot just focus on adopting one API technology quickly, they must have the flexibility to adopt any and all API technologies — and do it quickly at scale.
Flexibility, being able to switch between API technologies easily, allows multiple teams across the organization to move faster and adopt different architectures suited to their individual needs. Our expansion of full API lifecycle support for OAS 3.0 is part of our larger vision to expand our portfolio of available API technologies to allow organizations this flexibility. We want to let teams work in the technology they’re most comfortable with and fits their needs, adopting a new definition of agile where it’s all about choices and options, adopted quickly at scale.
Design, build, deploy, and manage OAS 3.0 APIs
As of last year, Anypoint Platform users have been able to design APIs using the OAS 3.0 format in API Designer and Studio 7.7. Users could import, edit, mock, and simulate calls to OAS 3.0 specifications directly within the platform. And, users could publish to Exchange or API Community Manager to collaborate and reuse these specifications across and outside of the organization. This helped organizations share OAS 3.0 specifications within their API communities to adopt industry standards, meet regulatory requirements, and drive developer adoption.
Today, we have added support for implementing APIs with the OAS 3.0 format in Studio, and deploying and managing them on the Mule runtime with API Manager. With Studio 7.8, we’ve introduced the ability to scaffold OAS 3.0 API specifications — jumpstarting the development process by automatically building the implementation routing for the defined methods and resources in the specification to Mule flows. We’ve also streamlined the transition from design to deploy by including support for testing and debugging these APIs within Studio. And finally, we’ve updated API Manager to allow management of APIs in the OAS 3.0 format, Mule and non-Mule, with API gateways and proxies.
Getting started with OAS 3.0 on Anypoint Platform
Download Studio 7.8 to get started building OAS 3.0 APIs on Anypoint Platform or visit the documentation to learn more about this release.