While working in Non-Mule assets like design API in Open API specification, there are few challenges to keep non-mule and mule assets together and one of them is OAS assets. OAS3.0 assets were not supported by the Anypoint Platform. Now, it is past.

In a recent upgrade in the platform, MuleSoft has started supporting OAS3.0 operation in Anypoint platform like design API specification OAS3.0, publish it in exchange and export in Anypoint studio.

Here are a few limitations of release to support OAS3.0…

• Anypoint platform supports to create an OAS 3 API specification or import one from Anypoint Exchange.
• With current support, it facilitates to convert OAS 3 APIs to RAML or OAS 2 to complete the API life cycle.
• Developers need to convert OAS 3 APIs to RAML or OAS 2 to complete the API life cycle.
• Developers need to follow and convert OAS 3 APIs to RAML or OAS 2 to complete the API life cycle, including applying policies and implementing API proxies with API Manager.
• Can be imported an OAS 3.0 API specification from Design Center as an editable API project in Studio.
• It can be downloaded and published an OAS 3 specification, and view the specification documentation in Anypoint Exchange.
• It can publish an OAS 3.0 specification and view the specification documentation.
• In most cases, any OAS 3.0 features that REST Connect does not support are ignored and the connector will not generate. In some cases, a connector can’t be generated. In all cases, API specifications are published normally from API Designer to Anypoint Exchange.

OAS 3.0 specification API designed in anypoint design center which supported HTTP verbs.

• Anypoint supports to publish specification to exchange…

• We can import assets from exchange to design center to develop or perform modification in OAS3 based design…

#mulesoft #api design #anypoint platform #oas 3.0