Report

Help us improve this tool

SOAP Request Debugger

Paste a SOAP HTTP request or envelope XML to inspect SOAPAction, Content-Type, version, operation name, and body payload.

O M T

Inspect SOAP requests before they hit production

SOAP integrations fail in subtle ways: the wrong SOAPAction header, a mismatched Content-Type, or a body element in the wrong namespace. This debugger accepts either a full raw HTTP request (method line, headers, blank line, XML body) or a standalone SOAP envelope. It reports HTTP metadata, detects SOAP 1.1 vs 1.2, names the first payload element under Body, and shows the serialized operation element for quick diffing.

Pair it with the SOAP Envelope Builder, SOAPAction Header Builder, and SOAP Fault Parser when tracing request/response cycles during WSDL-based services.

What gets extracted

  1. HTTP method and path when you paste a full request.
  2. Content-Type and SOAPAction when present in headers.
  3. Envelope version from the SOAP namespace URI.
  4. Operation element local name and namespace URI.
  5. Full XML of the first body child for copy/paste into other tools.

Frequently Asked Questions

Does this send my request to a server?

No. Parsing runs entirely in your browser with the DOM XMLParser API. Nothing is uploaded for inspection.

Can I paste only the XML without HTTP headers?

Yes. If the input does not start with an HTTP method line, the tool treats the entire paste as the SOAP envelope and still extracts version, operation, and body payload.

Why is the operation name empty?

The tool reports the first element child inside Body. An empty body, whitespace-only body, or malformed envelope yields no operation name until the XML is fixed.