Convert JSON to SOAP XML Online — Free Browser Tool

A modern REST service returns JSON. A legacy SOAP partner expects XML wrapped in a SOAP envelope. To bridge them quickly, convert the JSON to XML in your browser, then paste that XML inside a minimal SOAP envelope. This guide walks through the exact transformation, shows what the intermediate XML looks like, and covers the gaps between a browser converter and a real API gateway policy.

The Two-Step SOAP Conversion

SOAP XML is just regular XML wrapped in an <soap:Envelope> and <soap:Body>. So the workflow is:

1. Step 1 — paste your JSON into the JSON to XML converter. Set the root element name to match your operation, for example GetCustomerRequest.
2. Step 2 — drop the output into a SOAP envelope template. You only write the envelope once; the body changes per request.

Minimal SOAP 1.1 envelope:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <!-- paste converted XML here -->
  </soap:Body>
</soap:Envelope>

For SOAP 1.2, swap the namespace URI to http://www.w3.org/2003/05/soap-envelope. Your partner's WSDL tells you which version they expect.

A Real Example — Customer Lookup

You have REST JSON:

{"customerId":"C-3391","includeOrders":true,"region":"US-EAST"}

Set the root element to GetCustomerRequest, convert, and you get:

<GetCustomerRequest>
  <customerId>C-3391</customerId>
  <includeOrders>true</includeOrders>
  <region>US-EAST</region>
</GetCustomerRequest>

Wrap that in the SOAP envelope from the previous section and you have a body ready to fire at the service. Test it with Postman's raw XML body option or paste it into SoapUI.

Sell Custom Apparel — We Handle Printing & Free Shipping

What a Browser Tool Skips Versus a Real API Gateway

Apigee, IBM API Connect, Boomi, Azure API Management, and Mulesoft all ship a JSON-to-XML policy. Those policies handle attributes, namespaces, CDATA, and repeated elements according to configurable rules. A browser converter does one thing — turn JSON into well-formed XML — and that's it.

Use the browser tool for:

• Debugging a SOAP call before you have the gateway policy set up.
• Building test fixtures to paste into Postman or SoapUI.
• Writing documentation that shows the JSON-to-XML shape for a team.
• One-off conversions where wiring a full gateway is overkill.

If your real production flow requires SOAP headers with WS-Security, MTOM attachments, or namespace prefixes, configure it in your gateway. The browser converter gets you the body, not the envelope contract.

Handling Attributes That SOAP Actually Wants

Some SOAP schemas require attributes — <customer id="42"> rather than <customer><id>42</id></customer>. This converter outputs element-only XML. Two workarounds:

• Find-and-replace — if only a few fields need to be attributes, convert to elements first, then hand-edit. Fast for 2-3 attributes.
• XSLT post-processing — write a short transform that promotes specific elements to attributes on their parent. Reusable across requests.

For the full pattern-matching rules, see our JSON to XML with attributes guide.

When to Pick JSON Over SOAP and Move On

If you control the partner, push for a REST or GraphQL endpoint instead. SOAP's strengths — strict schemas, WS-Security, formal contracts — are rarely worth the tooling overhead in 2026. Most "we need SOAP" requirements boil down to a legacy system nobody wants to retire.

That said, when you can't change the contract, a browser converter plus a two-line envelope template gets you unblocked in a minute. Don't let XML be the reason you can't ship.

Frequently Asked Questions

Does this tool produce a full SOAP envelope?

No. It converts your JSON to well-formed XML. You wrap that XML in a SOAP envelope yourself — usually just 4 lines of boilerplate. This keeps the tool focused and transparent about what it does.

Can I convert JSON to SOAP XML for Apigee or Azure API Management?

Yes, for prototyping. For production, use the gateway's built-in JSON-to-XML policy because it handles namespaces and attributes according to your WSDL. The browser tool is great for debugging and building test requests.

My SOAP service needs a specific namespace — how do I add it?

After converting, add the namespace to your root element manually: . The converter outputs plain XML without namespaces so you have full control over how they're declared.

Will this work for SOAP 1.1 and SOAP 1.2?

The converter produces generic XML. Both SOAP 1.1 and 1.2 consume it the same way — you just change the envelope namespace. 1.1 uses schemas.xmlsoap.org, 1.2 uses www.w3.org/2003/05.