SOAP requests

Choose Add SOAP in a collection or a section. SOAP requests carry a SOAP stamp. The flow is close to SoapUI’s.

Load a WSDL and pick an operation

1. Enter the WSDL URL, or choose a file with Choose file, then press Load WSDL. Codestamp also reads wsdl:import, xsd:import and xsd:include.
2. Pick an operation from the dropdown, which reads Operation · Binding · SOAP 1.1/1.2.

Codestamp then fills the endpoint, the SOAPAction, the SOAP version, the request name, and a sample envelope. The sample has ? for each value, with the comments Optional, repetitions and CHOICE, as SoapUI writes them.

If you edit the envelope and then change the operation, Codestamp keeps your edit. Reset the envelope to the sample brings the sample back.

What Codestamp sends

• SOAP 1.1 goes out as text/xml with a SOAPAction header.
• SOAP 1.2 goes out as application/soap+xml; action="...".
• A header you type yourself wins.

A response that contains a SOAP Fault gets a SOAP Fault chip with the fault code and reason. Test scripts get xml2Json(), as in Postman, and there is a snippet called “SOAP: no fault, read the body”. See Scripts.

SOAP requests take part in Run all, the CLI and Orchestration. Export to Postman Collection v2.1 writes them as a plain POST with the SOAP headers.

Import a WSDL

On the Import page, a WSDL from a file or a URL becomes a new collection, with one section per binding and one SOAP request per operation. An address that clearly is a WSDL (?wsdl, ?singleWsdl or .wsdl) goes straight to the WSDL reader along with its imports. See Import and export.

Safety and limits

• A WSDL can load over plain http or https from any server, like the SOAP request itself, because many internal SOAP services publish their WSDL only over http. A WSDL fetched over http is not encrypted. Importing any other collection or spec from a URL still needs HTTPS, with http only for localhost.
• A WSDL file is read only when you pick it in the dialog, and its relative imports cannot leave the file’s folder.
• Codestamp rejects DTDs, so XML entity tricks such as XXE and “billion laughs” do not apply.
• The limit is 64 documents and 20 MB per WSDL.
• Not supported yet: WSDL 2.0, WS-Security (UsernameToken), a SOAP mock service, and WSDL that is not UTF-8.