Import WSDL

Fetchpier imports WSDL definitions for SOAP web services — SOAP 1.1 / WSDL 1.1 bindings only. Non-SOAP HTTP bindings and WSDL 2.0, including REST/JSON services, are not supported.

The WSDL can come from a local file, an HTTP(S) URL, or pasted raw text, chosen via tabs in the import wizard. The format is detected automatically from the input content (or you can pick it manually). The wizard prompts for a collection name (defaulting to the schema’s title) and a conflict strategy when the target collection already exists: merge (add the requests, skipping name collisions) or abort (change nothing and report the conflict).

What the import generates

Each operation becomes a POST request with a ready-to-edit SOAP envelope as a raw XML body, with XML highlighting. The body is generated from the WSDL’s embedded XSD schema — sample values per type (strings, numbers, booleans, dates) for every input parameter, in both document/literal and rpc/literal styles — rather than an empty placeholder.

Operations are placed directly in the collection folder: flat, one request per operation.

Warnings you may see

• When the same operation is exposed by several SOAP bindings (e.g. SOAP 1.1 and SOAP 1.2), it is collapsed into a single request — a SOAP 1.1 envelope — and an import warning lists the collapsed bindings.
• Non-SOAP HTTP bindings (GET/POST) are ignored, each with its own warning.
• When an operation is only available over SOAP 1.2, the generated SOAP 1.1 envelope may need manual adjustment, and a warning flags it.

The result summary reports how many requests, folders, and environment variables were created plus any per-operation warnings. For the full list of supported formats and the wizard, see the import overview.