WSDL to JSON

Summarize a SOAP WSDL contract as JSON.

0 chars
0 words
0 lines
0 chars
0 words
0 lines

WSDL to JSON Converter Online

A WSDL file describes a SOAP web service, but reading hundreds of lines of namespaced XML to find out which operations exist is slow. The WSDL to JSON converter parses the contract and returns a compact JSON summary of everything that matters: the operations, their input and output messages, the data types, the SOAP binding, and the endpoint address.

What you get

  • types – elements, complexTypes, and simpleTypes from the inline XML Schema. Each type lists its fields with name, type, and minOccurs/maxOccurs, and simpleTypes show their base type and enumeration values.
  • messages – the named messages and their parts, pointing to schema elements or types.
  • portTypes – the abstract interface: every operation with its documentation, input, output, and fault messages.
  • bindings – how the port type is carried over the wire: the binding style (document or rpc), the transport, and the soapAction of each operation.
  • services – the concrete endpoints: each port, the binding it uses, and its address URL.

Namespace prefixes such as tns: and xsd: are removed from references, so tns:GetForecastInput simply reads GetForecastInput.

How to read a WSDL quickly

Start at services to see where the service lives, follow the port's binding to bindings to learn the SOAP style and actions, then go to portTypes for the list of operations. Each operation's input and output lead you to messages, and the message parts lead to types, which tell you exactly what XML to send.

Use cases

Planning an integration with a legacy SOAP API, documenting a service for a team that works with REST, reviewing a vendor's contract changes, or generating request templates by hand without a heavy IDE.

Once you have real traffic, turn responses into JSON with SOAP to JSON. View the raw contract as a tree in the XML Viewer, check it with the XML Validator, or compare two versions of a WSDL with XML Diff.

Frequently Asked Questions

Yes. WSDL 1.1 documents (<definitions>) are summarized as messages, portTypes, bindings, and services with ports. WSDL 2.0 documents (<description>) use interfaces, bindings, and services with endpoints instead. The "version" field in the output tells you which one was detected.

No. The tool works entirely offline in your browser and does not download referenced files. Types defined inline in the <types> section are listed; for imported XSDs, paste the schema separately into an XML tool.

Look under services → ports → address (WSDL 1.1) or services → endpoints → address (WSDL 2.0). That is the URL the SOAP requests are posted to.

Paste the WSDL content, not the URL. Open the service's ?wsdl address in your browser, copy the XML, and paste it here — nothing is fetched or uploaded by the tool.