API import restrictions and known issues

About this list

When importing an API, you might come across some restrictions or identify issues that need to be rectified before you can successfully import. This article documents these, organized by the import format of the API.

Open API/Swagger

If you are receiving errors importing your Open API document, ensure you have validated it - either using the designer in the Azure portal (Design - Front End - Open API Specification Editor), or with a third-party tool such as Swagger Editor.

  • Only JSON format for OpenAPI is supported.
  • Schemas referenced using $ref properties can't contain other $ref properties.
  • $ref pointers can't reference external files.
  • x-ms-paths and x-servers are the only supported extensions.
  • Custom extensions are ignored on import and are not saved or preserved for export.


See this document for important information and tips related to OpenAPI import.


WSDL files are used to generate SOAP Pass-through APIs or serve as the backend of a SOAP-to-REST API.

  • SOAP bindings -Only SOAP bindings of style ”document” and “literal” encoding are supported. There is no support for “rpc” style or SOAP-Encoding.
  • WSDL:Import - This attribute is not supported. Customers should merge the imports into one document.
  • Messages with multiple parts - These types of messages are not supported.
  • WCF wsHttpBinding - SOAP services created with Windows Communication Foundation should use basicHttpBinding - wsHttpBinding is not supported.
  • MTOM - Services using MTOM may work. Official support is not offered at this time.
  • Recursion - Types that are defined recursively (for example, refer to an array of themselves) are not supported by APIM.


Currently, there are no known WADL import issues.