CodesBeautify

WSDL to JSON Parser

Read a WSDL contract as structured JSON, or jump straight to a flat table of operations and their SOAP actions.

WSDL
JSON
Runs locally in your browser

About the WSDL to JSON Parser

A WSDL file answers three questions: what operations exist, what goes in and out of each one, and what address to post to. Finding those answers by reading the raw document is slow, because the information is spread across portType, binding, message and service sections that reference each other by qualified name. This parser walks all of them and returns one JSON object with the sections side by side, resolving the tns: style references down to bare names so you can follow them without mental namespace arithmetic.

Operation summary mode does the joining for you. For every operation it reports the port type it belongs to, the input and output message names, the SOAP action taken from the matching binding, and the endpoint address taken from the service port that uses that binding. That single array is usually enough to start writing a client, or to diff two versions of a contract and see which operations were added.

Both WSDL 1.1 documents and the endpoint style used by later versions are read, and inline schema element names are listed so you can see what types the messages point at. Anything the file does not declare, such as a missing transport attribute, is simply left out rather than filled with a guess. Once you know which operation to call, SOAP to JSON makes its responses readable, and XML Formatter tidies the WSDL itself.

How to use

  1. Paste the contents of the .wsdl file, or upload it.
  2. Start with Operation summary to see every operation, its messages and its endpoint in one array.
  3. Switch to Full contract for services, bindings, port types and message parts in detail.
  4. Copy the JSON or download it to keep alongside your client code.

Common questions

Does it support imported schema files?
Only what is inside the document you paste. WSDL files that import an external xsd will show the element names they reference but not the imported definitions.
Where does the SOAP action come from?
From the soapAction attribute on the soap:operation element inside the binding that matches the port type of that operation.
Why is my endpoint address empty?
That happens when no service port references the binding for that operation, which is common in contracts that leave the address to deployment configuration.
Can it generate client code?
No. It reports the contract as JSON so you can read or diff it. Code generation belongs to your language toolchain.