Test a SOAP service from its WSDL

Import a SOAP service's WSDL and get one ready request per operation, with its envelope, action and checks written for you.

In short

A SOAP service describes itself in a WSDL file. Import that file - or its address - and each operation becomes a request: the XML envelope is written from the service's own types, the action goes where its SOAP version expects it, and two checks come along: the answer is 200 and holds no SOAP fault. You see a preview before anything is saved, and History can undo the import.

Before you start

• A WSDL 1.1 description, as a .wsdl or .xml file, or its address - most services publish it at their address followed by ?wsdl.
• The file can be up to 10 MB.
• Who: signed in with API Tester on. Importing into an existing project needs Edit on it.
• Plan: a new project counts toward your plan's project limit.

Steps

1. Open the chevron beside "New request" and choose "Import a package…".
2. Under "Format", choose "SOAP service (WSDL)".
3. Drop the file or choose it - or type the WSDL's address under "Or fetch it from an address" and press "Fetch".
4. Read the preview and its warnings, untick what you do not want, and press "Import N selected".
5. Open a request, replace each ? in the envelope with a real value, and press "Send".

Result: one request per operation, grouped by service, calling {{baseUrl}} on the service's address.

What comes along

Good to know

• When a service offers an operation over both SOAP 1.1 and 1.2, it is imported once, over SOAP 1.1.
• Files the WSDL refers to (imported schemas) are not fetched; values of the types defined there are written as ? and a warning names the files.
• Plain HTTP bindings and operations that only send messages are left out, each said in a warning.
• Importing the same WSDL again matches the same requests, so "Replace" or "Skip" do what they say.
• A WSDL is import only. To move a project on, export a {{brand}} package, Postman, OpenAPI or YAML files.

If something goes wrong

• "The file is not a WSDL 1.1 description" - check that you saved the WSDL itself, not a page about it.
• "WSDL 2.0 descriptions cannot be imported" - ask the service for its WSDL 1.1 description.
• "The WSDL describes no SOAP operation to import" - the file has no port with a SOAP binding.
• "The file is not well-formed XML (line N, position M)" - fix the XML at that place and import again.
• The check that the answer holds no SOAP fault fails - the service answered with a fault; read its faultstring in the answer.