New in XMLSpy 2027

The HTTP Testing Window in XMLSpy now supports sending multipart/form-data POST and PUT requests. This content type is the standard way web APIs accept file uploads and requests that combine several kinds of data, such as text fields, JSON, and binary files, in a single message. Each part of the request carries its own name, headers, and content type, which makes it more flexible than a simple key-value form submission.

The HTTP Testing Window now includes entry helpers for building a multipart request. For each part, you specify a name, choose whether it is a text value or a file, set its content type, and then enter the text or select the file to upload.

You can add as many parts as the API expects, so uploading multiple files in one request, or sending a file together with its JSON metadata, is now a matter of filling in a few rows in the HTTP Testing Window.

The OpenAPI wizard has also been updated to handle this content type. When you generate a test request from an OpenAPI definition whose operation declares a multipart/form-data request body, XMLSpy reads the schema for that operation and pre-populates the form part editor with the expected parts, including their names and types. You can then fill in values and file paths, send the request, and inspect the response in the same window, exactly as with any other request type.

The HTTP Testing Window now covers the full range of requests a typical API accepts, from JSON bodies and simple forms to file uploads and mixed-content requests. Build the request by hand or generate it from your OpenAPI definition, then send it and inspect the response, all in one window.

When an OpenAPI document contains schemas, they can now be viewed and edited directly in the graphical XMLSpy JSON Schema Editor. Simply toggle to Schema view while working on an OpenAPI document and the schemas will be listed.

Clicking the schema icon next to a schema in the list opens its graphical detail view.

OpenAPI documents typically define the structure of request and response bodies as JSON Schema, either inline or under components/schemas. You can now select any of these schema definitions directly in an OpenAPI document and use it to validate a JSON instance or generate a sample. This lets you check a request payload or produce a realistic sample response without extracting the schema into a separate file.

XMLSpy supports OIM 1.0, including validation and conversion of xBRL-CSV reports. Now it can also render human-readable tables as XML or HTML directly from xBRL-CSV documents, just as it does for XML-based XBRL files.

XMLSpy supports seamless integration in the Eclipse IDE with new support added for the latest versions: