SOAP Request Tester

Server assisted API Testing

Build SOAP envelopes from a template, set SOAPAction and content type, send the request and read the response with pretty-printed XML and fault extraction.

Privacy: Processing happens in your browser where possible. Network checks are relayed through the Mutqan backend and are not stored.

What is SOAP?

SOAP is an XML-based messaging protocol for web services: every request and response is an Envelope with an optional Header and a Body, and the operations and types are described by a WSDL document. It is still common in banking, government and enterprise integration, where strict schemas and WS-* extensions for signing and encryption matter more than payload size.

How to use SOAP Request Tester

  1. Enter the service URL and choose the SOAP version.
  2. Pick a demo template or open the envelope builder and generate an envelope from operation + parameters, or paste your own.
  3. Set the SOAPAction if the service requires one.
  4. Send and read the fault box (if any) and the formatted XML response.

SOAP Request Tester features

  • SOAP 1.1 and 1.2 with the correct Content-Type and SOAPAction handling
  • Envelope builder: operation, namespace, JSON parameters and optional WS-Security UsernameToken
  • Envelope check (well-formedness, version, body element, namespaces) and XML formatter
  • Fault extraction (faultcode/faultstring, Code/Subcode/Reason) shown above the response
  • Pretty-printed XML response with raw view and header table

SOAP Request Tester example

Call a calculator service

Input:

POST http://www.dneonline.com/calculator.asmx
SOAPAction: "http://tempuri.org/Add"
<soapenv:Envelope …><soapenv:Body><tns:Add><tns:intA>7</tns:intA><tns:intB>5</tns:intB></tns:Add></soapenv:Body></soapenv:Envelope>

Output:

200 OK · SOAP 1.1 response · Body element: AddResponse
<soap:Envelope …>
  <soap:Body>
    <AddResponse xmlns="http://tempuri.org/">
      <AddResult>12</AddResult>
    </AddResponse>
  </soap:Body>
</soap:Envelope>

Frequently asked questions about SOAP Request Tester

What is the difference between SOAP 1.1 and 1.2 here?

SOAP 1.1 sends Content-Type: text/xml plus a SOAPAction header; SOAP 1.2 sends application/soap+xml with the action inside the Content-Type. Pick the version and the tool sets the headers and envelope namespace.

Can I build the envelope from parameters?

Yes. Open the envelope builder, enter the operation name, namespace and a JSON object of parameters (nested objects and arrays become child elements) and generate the envelope. Optional WS-Security UsernameToken headers are supported.

How are faults shown?

SOAP Faults (1.1 faultcode/faultstring and 1.2 Code/Reason/Subcode) are extracted and shown above the formatted XML response.

Do I need a WSDL?

No. The tool works with plain envelopes; use your WSDL to know the operation names and namespaces.

Technical notes

SOAP 1.1 requests use text/xml; charset=utf-8 and a quoted SOAPAction header. SOAP 1.2 requests use application/soap+xml; charset=utf-8; action="…". Null parameters are emitted as xsi:nil="true" elements.

References