SOAP & WSDL

Vegha supports SOAP web services. You can import a WSDL document to generate a ready-to-run collection, or compose SOAP envelopes directly.

SOAP versions

Vegha supports both SOAP 1.1 and SOAP 1.2. The version determines the envelope namespace and the way the action is conveyed, and Vegha handles the differences for you when a request is built from a WSDL.

Importing a WSDL

The fastest way to start is to import the service’s WSDL. Vegha reads the WSDL and generates an executable collection:

1. Import the WSDL document.
2. Vegha creates a collection containing one request per operation defined in the WSDL.
3. Each generated request is pre-filled with the correct endpoint, SOAP version, and a skeleton envelope for that operation.

This turns a WSDL into a usable set of requests without hand-writing envelopes. See the importer documentation for the full list of supported import formats.

The SOAP envelope editor

A SOAP request body is a SOAP envelope — an XML document with a header and a body. The envelope editor provides XML editing with syntax highlighting so you can fill in the operation’s parameters inside the Body element. For WSDL-generated requests, the skeleton is already in place; you just supply values.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Header/>
  <soap:Body>
    <GetUser xmlns="http://example.com/users">
      <id>42</id>
    </GetUser>
  </soap:Body>
</soap:Envelope>

Namespaces

SOAP relies heavily on XML namespaces — for the envelope itself and for the operation’s message types. When a request is generated from a WSDL, the required namespaces are included. If you compose an envelope by hand, declare the namespaces the service expects, otherwise the server may reject the message.

Headers and authorization

A SOAP request is sent over HTTP, so the standard tabs apply. Set HTTP headers on the Headers tab and choose an auth method — including WSSE, which is common for SOAP services — on the Authorization tab. See Authentication.

You can use {{variable}} interpolation in the endpoint URL and inside the envelope body.

Tip

Importing the WSDL is almost always better than starting blank — it gives you correct endpoints, the right SOAP version, and valid envelope skeletons for every operation.