SOAP Formatter

SOAP Formatter – Readable SOAP Messages

SOAP web services exchange XML envelopes that are usually logged or captured without any line breaks. The SOAP formatter pretty-prints SOAP 1.1 and 1.2 messages so you can read headers, bodies, and faults while debugging an integration.

What is a SOAP message?

Every SOAP message is an XML document with an Envelope root element. The optional Header carries metadata such as authentication tokens, WS-Security signatures, or WS-Addressing information. The Body contains the actual request or response payload, or a Fault element describing an error. Namespaces like soap: or soapenv: identify the SOAP version.

How to use the formatter

Paste a SOAP request or response — copied from SoapUI, Postman, a server log, or the browser's network panel — and the formatted envelope appears instantly. Choose indentation and whether comments are kept, then copy or download the result.

Debugging tips

• Faults – look for faultcode / faultstring (SOAP 1.1) or Code / Reason (SOAP 1.2) inside the body.
• Namespaces – most "unknown element" errors come from a payload element in the wrong namespace. Formatting makes the xmlns declarations easy to compare with the WSDL.
• Security headers – formatted WS-Security headers show timestamps, usernames, and binary tokens clearly. Remove credentials before sharing a formatted message.

Strict parsing

The formatter uses a strict XML parser, so a truncated log entry or a broken envelope is reported with the line and column instead of being silently "fixed".

Related tools

Summarize a service description with the WSDL Formatter or WSDL to JSON, convert a SOAP payload to JSON with SOAP to JSON, or minify messages again with the XML Minifier.