The release notes for the latest version of Postman show the below statement.
You can now import WSDL specification into Postman
Can anyone please help how we can import WSDL specifications into postman?
Does this mean, the request will automatically be generated in postman for SOAP endpoints?
One way that you can do this, is by using the Import > Raw Text feature. This will create a new Collection based on the information in the schema.
I grabbed this example from here: https://tomd.xyz/wsdl/
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.cleverbuilder.com/BookService/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
name="BookService"
targetNamespace="http://www.cleverbuilder.com/BookService/">
<wsdl:documentation>Definition for a web service called BookService,
which can be used to add or retrieve books from a collection.
</wsdl:documentation>
<!--
The `types` element defines the data types (XML elements)
that are used by the web service.
-->
<wsdl:types>
<xsd:schema targetNamespace="http://www.cleverbuilder.com/BookService/">
<xsd:element name="Book">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ID" type="xsd:string" minOccurs="0"/>
<xsd:element name="Title" type="xsd:string"/>
<xsd:element name="Author" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Books">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="tns:Book" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="GetBook">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ID" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="GetBookResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="tns:Book" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="AddBook">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="tns:Book" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="AddBookResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="tns:Book" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="GetAllBooks">
<xsd:complexType/>
</xsd:element>
<xsd:element name="GetAllBooksResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="tns:Book" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<!--
A wsdl `message` element is used to define a message
exchanged between a web service, consisting of zero
or more `part`s.
-->
<wsdl:message name="GetBookRequest">
<wsdl:part element="tns:GetBook" name="parameters"/>
</wsdl:message>
<wsdl:message name="GetBookResponse">
<wsdl:part element="tns:GetBookResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="AddBookRequest">
<wsdl:part name="parameters" element="tns:AddBook"></wsdl:part>
</wsdl:message>
<wsdl:message name="AddBookResponse">
<wsdl:part name="parameters" element="tns:AddBookResponse"></wsdl:part>
</wsdl:message>
<wsdl:message name="GetAllBooksRequest">
<wsdl:part name="parameters" element="tns:GetAllBooks"></wsdl:part>
</wsdl:message>
<wsdl:message name="GetAllBooksResponse">
<wsdl:part name="parameters" element="tns:GetAllBooksResponse"></wsdl:part>
</wsdl:message>
<!--
A WSDL `portType` is used to combine multiple `message`s
(e.g. input, output) into a single operation.
Here we define three synchronous (input/output) operations
and the `message`s that must be used for each.
-->
<wsdl:portType name="BookService">
<wsdl:operation name="GetBook">
<wsdl:input message="tns:GetBookRequest"/>
<wsdl:output message="tns:GetBookResponse"/>
</wsdl:operation>
<wsdl:operation name="AddBook">
<wsdl:input message="tns:AddBookRequest"></wsdl:input>
<wsdl:output message="tns:AddBookResponse"></wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetAllBooks">
<wsdl:input message="tns:GetAllBooksRequest"></wsdl:input>
<wsdl:output message="tns:GetAllBooksResponse"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<!--
The `binding` element defines exactly how each
`operation` will take place over the network.
In this case, we are using SOAP.
-->
<wsdl:binding name="BookServiceSOAP" type="tns:BookService">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="GetBook">
<soap:operation
soapAction="http://www.cleverbuilder.com/BookService/GetBook"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AddBook">
<soap:operation
soapAction="http://www.cleverbuilder.com/BookService/AddBook"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetAllBooks">
<soap:operation
soapAction="http://www.cleverbuilder.com/BookService/GetAllBooks"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<!--
The `service` element finally says where the service
can be accessed from - in other words, its endpoint.
-->
<wsdl:service name="BookService">
<wsdl:port binding="tns:BookServiceSOAP" name="BookServiceSOAP">
<soap:address location="http://www.example.org/BookService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
That would look like this in the app:
Hi @danny-dainton,
Thank you!
I found another way to import wsdl by using url to import and provide directly the wsdl url. This also works.
Now life is bit simpler with all these 
You should also be able to import with a file too 
Yeahh!
I hope it also supports multiple imported schemas within WSDL, which I am yet to try 
Hello,
Unfortunately, the paint isn’t dry yet on this feature, and all WSDL don’t work:
Hope it’s going to be fixed soon!
You can now import WSDL specification split across multiple files with Import > Folder flow. Just make sure all imports are present locally on machine with the correct schema location.
Good to hear… I will definitely give a try for cross reference wsdl import 
There’s another WSDL update here - https://blog.postman.com/postman-now-supports-wsdl/ you can import WSDL as an API now and collaborate and generate documentation, collections, mock servers and tests against it like other schemas as OpenAPI,RAMLs, etc.
Can someone help me on steps to import the below sample WSDL. I tried copy paste and import URL also but nothing works, It only imports an API and no collection is created
Sample URL : MFOrder Service
WSDL File : https://bsestarmfdemo.bseindia.com/MFOrderEntry/MFOrder.svc?singleWsdl
Hello,
after import of a WSDL file, I only got the API Calls, but the import is not able to read the request parameters, so I also have to add all parameters by hand.
Does anybody now why?`
In SoapUI I can add a link to an wsdl and then I got the complety structure and I only has to add the parameter values.
@pshflorian same issue. Help !
Hi @mayank.lavania,
It took me a while, but there could be cyclic reference in wsdl schema. Also, I am not fully sure.
Hi @danny-dainton, it seems even new update 8.11.1 also don’t support WSDL which have cyclic references.
Any progress here on the cyclic reference support in wsdl schema and what about WS-Adressing support?
Well i have wsdl which is protected (it means when i hit that wsdl url in broswer it asked for username and password ) and same i have to import in postman is their any way?
Same for me except I only got 2 methods (out of about 20) and with no parameters. Again SOAP UI has no problem.
