Postman Now Supports WSDL

Update: This post was originally published to announce the introduction of WSDL import support in Postman. WSDL import is now a long-standing capability that allows teams to generate and work with SOAP requests in Postman.

We’re excited to announce that Postman now supports WSDL (Web Services Description Language) files, adding to the multiple API specification formats that we already support. This has been one of the oldest open feature requests on our issue tracker and a common ask from our users.

With this capability, you can import WSDL files, generate SOAP requests, and collaborate on testing and debugging SOAP services using Postman’s familiar collections and workspaces.

If you’re a developer working with multiple services spread across different architectural patterns and software standards, you know how cumbersome it is to work across different tools. With this update, you can use Postman to test, debug, and collaborate on SOAP-based web services alongside other API styles in a single workspace. Plus, you can leverage our powerful, expansive Postman API Network to enable discovery within your organization or team, and publish publicly available APIs in public workspaces.

Save time testing your services

Import your WSDL files directly into Postman (both WSDL 1.1 and 2.0 are supported) and use generated collections to send requests, inspect the response, and easily debug your services. Postman will automatically generate the SOAP envelopes that conform to the structure defined in the specification, eliminating the need to manually craft requests for each operation:

Define your SOAP services as Postman APIs

Define WSDL as the underlying specification used to generate collections and documentation in Postman. This lets you link generated requests to user-facing documentation for service consumers, monitors to track service metrics, and mocks that consumers can use to unblock their client development:

Validate your collections, documentation, and tests against the WSDL schema

A major source of quality issues is a disparity between the stated API specification and actual traffic your service handles. The Postman API platform can now help you address this. Validating Postman Collections against your schema will let you identify undocumented endpoints/operations, and even incorrect parameters in your SOAP envelope.

We’d love to hear what you think about this new feature. Reach out to us on GitHub, leverage our Postman Community forum to engage with other Postman users, or contact us at [email protected] to share your thoughts and feedback around your use cases.

Try Postman now