SOAP Response Parser
Parse a SOAP envelope: the body's element name, the header count, and the fault code and reason when the response is a fault.
What the SOAP Response Parser does
The envelope is read into a tree and the Body is searched by local name, so both the SOAP 1.1 and 1.2 envelope prefixes resolve. The first child of the Body that is not a Fault is the payload, and its name is reported rather than its text, because that is what tells you which operation answered.
A Fault is read for both spellings: SOAP 1.2's Code/Value and Reason/Text, and SOAP 1.1's faultcode and faultstring.
This reads the envelope's structure, not its meaning: the payload is not parsed further, and a fault's detail element is not interpreted. It does not verify anything about the response.
How to use it
Paste the envelope into the SOAP envelope box, or press Run with the example already there.
Read the Response report below: the body element, the header count and whether it is a fault.
Check the Response report Fault lines on a failure — the code and reason are usually the only place a SOAP service explains itself.
Worked example
Input:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><GetUserResponse><name>Ada</name></GetUserResponse></soap:Body></soap:Envelope>
Output:
Body element: GetUserResponse
Headers: 0
Fault: no
Why it runs in your browser
The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.
What a SOAP response actually contains: the body's payload element, how many header blocks arrived, and — when the response is a fault — the code and the reason.
An envelope with no Body is refused, because a report with no payload would read like an empty success.
What it does, and what it does not
The envelope is read into a tree and the Body is searched by local name, so both the SOAP 1.1 and 1.2 envelope prefixes resolve. The first child of the Body that is not a Fault is the payload, and its name is reported rather than its text, because that is what tells you which operation answered.
A Fault is read for both spellings: SOAP 1.2's Code/Value and Reason/Text, and SOAP 1.1's faultcode and faultstring.
This reads the envelope's structure, not its meaning: the payload is not parsed further, and a fault's detail element is not interpreted. It does not verify anything about the response.
How to use SOAP Response Parser
Paste the envelope into the SOAP envelope box, or press Run with the example already there.
Read the Response report below: the body element, the header count and whether it is a fault.
Check the Response report Fault lines on a failure — the code and reason are usually the only place a SOAP service explains itself.
What to Expect
Best for
- Reading which operation answered a request
- Getting a fault code and reason without reading XML
Not ideal for
- Parsing the payload's own fields
- Verifying a signed response
What this tool keeps
- The payload element's qualified name
- Both SOAP 1.1 and 1.2 fault spellings
What may need cleanup
- The payload still needs its own parser
- A fault's detail element needs reading by hand
Common errors
- The page refuses it: the envelope has no Body element
Example use cases
- Debugging a SOAP integration
- Reading a fault from a captured response
Sample input
SOAP envelope: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><GetUserResponse><name>Ada</name></GetUserResponse></soap:Body></soap:Envelope>
Sample output
Response report: Body element: GetUserResponse …
Who this is for
- Developers integrating a SOAP service
- Anyone reading a legacy API's error
Frequently asked questions
Why is the payload name reported instead of its content?
The name tells you which operation answered and whether the service wrapped the result as expected. The payload's fields belong to the service's own schema, which this page does not know.
Which SOAP versions are read?
Both. The envelope is matched by local name, and the fault is read with either the 1.2 Code/Reason shape or the 1.1 faultcode/faultstring one.
Does it show HTTP status?
No. A SOAP response is an HTTP body; the status line belongs to the transport and is not part of the envelope.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.