WSDL/XSD Analyzer & SOAP Request Validator

Import a WSDL file — with embedded or separate XSD schemas — to browse services, ports and operations. Generate ready-to-use SOAP 1.1 or 1.2 request examples, then paste and validate any SOAP XML against the XSD definitions, all in your browser.

Load a WSDL file to explore services and operations
Select an operation from the tree to view details
Overview
Generate Request
Validate XML

What is WSDL and XSD?

WSDL (Web Services Description Language) is an XML-based format that describes a SOAP web service — its operations, input/output messages, bindings and network endpoints. XSD (XML Schema Definition) defines the data types and structure of the XML messages the service exchanges. Together they form the machine-readable contract for SOAP-based web services.

This tool parses WSDL 1.1 documents and their XSD schemas (embedded in wsdl:types or uploaded separately), builds a browsable service/operation tree, generates valid SOAP 1.1 and 1.2 request examples, and validates XML against the schema definitions — entirely in your browser with no server upload.

How to Use

  1. Load WSDL — Click "Load WSDL" and pick your .wsdl or .xml file. The tool immediately parses and builds the operation tree.
  2. Add XSD files (optional) — If your WSDL references external schema files via xsd:import, click "Add XSD files" and select them. They are merged into the type registry automatically.
  3. Select an operation — Click any operation in the left tree.
  4. Generate a SOAP request — Go to the "Generate Request" tab for a ready-to-use SOAP envelope with type-correct placeholder values.
  5. Validate XML — Paste any SOAP XML in the "Validate XML" tab and click Validate to check it against the operation's XSD schema.

Supported Features

WSDL 1.1 Parsing

Parses all major WSDL 1.1 constructs: wsdl:service, wsdl:port, wsdl:binding, wsdl:portType, wsdl:operation and wsdl:message. Handles document/literal and rpc/literal binding styles. Detects SOAP 1.1 and SOAP 1.2 bindings automatically.

XSD Type Registry

All xsd:element, xsd:complexType and xsd:simpleType definitions — embedded in wsdl:types or from uploaded XSD files — are indexed in a unified type registry. Type references are resolved recursively, including xsd:sequence, xsd:all, xsd:choice, xsd:complexContent with extension and restriction.

SOAP Request Generation

Builds a complete SOAP 1.1 or 1.2 envelope populated with semantically correct placeholder values: dates, booleans, integers, URIs, base64 and enumeration values all get type-appropriate examples. Namespace declarations are injected automatically.

XSD Structural Validation

Validates SOAP XML against XSD schema rules: required elements (minOccurs), element ordering in sequences, cardinality (maxOccurs), xsd:choice constraints, enumeration restrictions, and basic type checks for integers, decimals, booleans, dates and datetimes. Also verifies SOAP envelope structure (Header, Body presence).

Example Use Cases

Explore a legacy SOAP service

1. Load your .wsdl file
2. Browse services and ports in the tree
3. Click each operation to see its details
4. Copy generated SOAP to use in Postman or SoapUI

Validate a SOAP response

1. Load WSDL + XSD files
2. Select the operation that sent the response
3. Paste the raw SOAP XML in "Validate XML"
4. → Errors shown with exact element paths

Frequently Asked Questions

WSDL 1.1 is fully supported — the most widely used version, produced by Apache Axis, .NET WCF, IBM WebSphere and others. WSDL 2.0 is not yet supported.

Yes. All parsing and processing happens entirely in your browser using the native DOMParser API. Your WSDL, XSD files and XML payloads never leave your device. The tool works offline once the page is loaded.

After loading the WSDL, click "Add XSD files" and select all referenced .xsd files. The tool adds them to the type registry and they immediately become available for SOAP generation and validation. You can add as many XSD files as needed in one go (multi-select is supported).

document/literal (recommended modern style, used by WCF and Axis2) and rpc/literal are fully supported. The older rpc/encoded style shows the operation tree but type-based generation may be limited since encoded types are not in the XSD registry.

It checks: required elements (minOccurs ≥ 1), element ordering in xsd:sequence, element cardinality (maxOccurs), xsd:choice constraints, xsd:enumeration allowed values, and basic type checks for integer, decimal, boolean, date and dateTime. Full facet validation (patterns, string lengths, etc.) is not yet supported.

Yes. The validator accepts envelopes using the SOAP 1.1 namespace (http://schemas.xmlsoap.org/soap/envelope/) or the SOAP 1.2 namespace (http://www.w3.org/2003/05/soap-envelope). It detects the version automatically from the <Envelope> namespace and validates the body content against the selected operation's schema.