SOAP to JSON Converter

Convert SOAP XML envelopes to clean JSON. Automatically strips the SOAP wrapper and extracts the body content for SOAP 1.1 and 1.2 messages.

Last updated: May 28, 2026

Extract Body OnlyInclude Attributes

Indent:

SOAP XML Input

JSON Output

XML parsing requires a browser environment

Client-Side Processing

Input Data Stays on Device

Instant Local Execution

Find this tool useful? Support the project to keep it free!

Buy me a coffee

What is SOAP to JSON Converter?

SOAP (Simple Object Access Protocol) is an XML-based messaging protocol widely used in enterprise web services, banking APIs, ERP integrations, and government systems. Every SOAP message is wrapped in a standardised XML envelope — a Envelope element containing an optional Header and a required Body. When you receive a SOAP response, the actual payload data is buried several levels deep inside this boilerplate wrapper.

This SOAP to JSON converter extracts the content of the SOAP Body and converts it to clean, readable JSON. It supports both SOAP 1.1 (`http://schemas.xmlsoap.org/soap/envelope/`) and SOAP 1.2 (`http://www.w3.org/2003/05/soap-envelope`), and automatically detects SOAP Fault responses so you can identify errors immediately.

How to Use SOAP to JSON Converter

Paste your SOAP XML response into the input area on the left

The tool detects whether SOAP 1.1 or 1.2 is used and shows a version badge

The JSON output (body content only by default) appears on the right instantly

Toggle "Extract Body Only" off if you want the full envelope including headers in the output

Toggle "Include Attributes" off to skip XML attributes from the JSON output

Click "Copy JSON" to copy the result or "Download .json" to save it

Common Use Cases

Parsing SOAP API responses from banking or financial web services
Extracting data from ERP system SOAP responses (SAP, Oracle, Microsoft Dynamics)
Debugging SOAP Fault messages by converting them to readable JSON
Converting legacy SOAP endpoint responses for use in modern JavaScript applications
Testing SOAP web services and inspecting response payloads
Migrating data from SOAP-based systems to REST/JSON APIs

Example Input and Output

A typical SOAP 1.1 GetWeather response being converted to clean JSON:

SOAP XML input

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header/>
  <soapenv:Body>
    <GetWeatherResponse>
      <City>London</City>
      <Temperature unit="C">18</Temperature>
      <Condition>Partly cloudy</Condition>
      <Humidity>72</Humidity>
    </GetWeatherResponse>
  </soapenv:Body>
</soapenv:Envelope>

JSON output (body only)

{
  "City": "London",
  "Temperature": {
    "@unit": "C",
    "#text": "18"
  },
  "Condition": "Partly cloudy",
  "Humidity": "72"
}

How This Tool Works

The XML input is parsed with the browser's native DOMParser. The tool inspects the root element's namespace URI to determine the SOAP version (1.1 or 1.2). When "Extract Body Only" is enabled, it locates the Body element using getElementsByTagNameNS and recursively converts its child elements to JSON objects. Repeated siblings become arrays, attributes become @-prefixed keys, and text nodes become string values.

Technical Stack

Browser DOMParser APISOAP 1.1 and 1.2 namespace handlingRecursive DOM traversalClient-side only

Privacy First

SOAP parsing runs entirely in your browser. Your SOAP payloads — which commonly contain sensitive financial, healthcare, or business data — are never transmitted to our servers.

WS-Security Headers

If your SOAP envelope includes WS-Security headers (wsse:Security, xenc:EncryptedKey), those will appear in the JSON output only if "Extract Body Only" is turned off. The body-only mode skips all header elements and focuses on the business payload.

Frequently Asked Questions

What is the difference between SOAP 1.1 and SOAP 1.2?

SOAP 1.1 uses the namespace http://schemas.xmlsoap.org/soap/envelope/ and is the older, more widely deployed version. SOAP 1.2 uses http://www.w3.org/2003/05/soap-envelope and is the W3C standard version with better HTTP binding and improved fault codes. Both are supported by this tool, which auto-detects the version from the Envelope namespace.

What is a SOAP Fault and how is it shown?

A SOAP Fault is a standardised error response. When detected (a Fault element inside the Body), the tool shows a yellow Fault badge alongside the SOAP version indicator. The fault code, fault string, and detail element are all included in the JSON output so you can inspect the error.

Why does my SOAP XML not get body-only extraction?

Body-only extraction requires a recognisable SOAP Envelope root element. If the tool cannot find the SOAP namespace, it falls back to converting the full XML document to JSON. You can also manually toggle "Extract Body Only" off to convert the full document.

How are XML namespace prefixes handled?

Namespace prefixes in element names (like soapenv:Body) are simplified to their local names in body-only mode. Attributes including xmlns declarations are preserved with the @ prefix by default. You can toggle attribute inclusion off if you want a cleaner output without namespace declarations.

Is my SOAP data sent to a server?

No. All parsing and conversion runs entirely in your browser using the native DOMParser API. Your SOAP payloads — which may contain sensitive business data, credentials, or API responses — never leave your machine.