Inspect a SOAP XML response
Paste a SOAP response, navigate the Envelope and Body, and run an XPath query to pull out the value you need — even when elements are namespaced.
Open the tool, then paste the sample input below. Everything runs locally in your browser.
The problem
A SOAP response wraps the payload in an Envelope and Body, often with namespace prefixes, so the value you want is buried. Reading it by eye is slow and XPath against namespaced nodes is fiddly. An inspector lets you navigate the tree and test an XPath to extract exactly the field.
Sample input
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<getPriceResponse>
<price>42.50</price>
</getPriceResponse>
</soap:Body>
</soap:Envelope>Expected output
//getPriceResponse/price -> 42.50The value lives inside soap:Body. The soap: prefix is a namespace; the unprefixed getPriceResponse element is matched directly to reach the price.
How to do it
- Paste the SOAP XML response.
- Expand the Envelope and Body.
- Write an XPath to the value you need.
- Run the XPath and read the result.
- Copy the extracted value.
Common mistakes
- Forgetting the payload is nested inside the SOAP Body.
- Ignoring namespace prefixes when writing the XPath.
- Matching a default-namespace element without binding the namespace.
- Assuming one result when the XPath matches several nodes.
- Treating attributes and element text the same way.
Related tools
Related guides
FAQ
How do I get a value out of a SOAP response?
Navigate into the soap:Body to the payload element and run an XPath to the field you need. The inspector shows the tree so you can build the path.
How do I handle namespaces in the XPath?
Namespaced elements carry a prefix like soap:. Bind the prefix or match the local name; an XPath that ignores the namespace will not select the node.
Where is the payload in a SOAP response?
Inside soap:Envelope then soap:Body. The operation response element, such as getPriceResponse, holds the actual fields.
What if my XPath matches multiple nodes?
XPath returns a node set, so a path can match several elements. Make the path more specific or index into the result to get one value.
Is my response uploaded?
No. Parsing and XPath evaluation run locally in your browser. Your response is not sent to a server.
SOAP/XML inspection runs locally in your browser. Nothing is uploaded.
Inspect XML and SOAP, convert to JSON, query and format payloads — grouped in one place.