Azure API Management has just introduced preview support of OpenAPI Specification v3 – the latest version of the broadly used open-source standard of describing APIs. Implementation of the feature is based on the OpenAPI.NET SDK.

The new Versions and Revisions feature was designed to fit as seamlessly as possible into our existing management API. From a high level perspective, working with a current Revision is identical to the way working with an API has always been.

The set body policy is used for changing the request or response body. If the policy is in the inbound policy section it changes the request payload passed to the back-end API, however, if it is in the outbound section it changes the response payload returned by API Management to the client.

Today we are excited to announce the public preview of support for Versions and Revisions in Azure API Management! This new feature gives you flexibility and control in how you manage change and the lifecycle of your API.

A few months ago we added SOAP pass-through support to Azure API Management - thank you to all of you using and giving us feedback on this feature. One of the top requests was, "How can I transform my SOAP backend into a RESTful HTTP front end?"

Over the past few years, an API description format called Swagger has quickly gained momentum. In order to reach it's full potential the specification was recently donated by its owner Smartbear, to the OpenAPI Initiative group.

Many of our customers have requested the ability to use Azure API Management to create a proxy for their SOAP APIs in the same way that we allow them to for REST/HTTP APIs, enabling developer portal integration, analytics, policies etc