Choosing a body type
Open a request node, go to Body and pick the type at the top:
Quixa sets the
Content-Type header for the body itself (for multipart it includes the boundary), so you do not need to add one.
Bindings (
{{CreateCustomer.response.id}}), QMock values ({{QMock.person.firstName}}) and QPlugin calls work in form field values and in raw bodies, exactly as in JSON bodies.Files
In a multipart form, set a field’s type to File, then:- Upload a file from your computer, or
- Choose a file your workspace uploaded earlier.
- Files belong to your workspace; other workspaces cannot read or reference them.
- File contents never appear in execution results or logs; only the field name and file name are shown.
- The default limit is 25 MB per file. Accepted types include PDF, images (PNG, JPEG, GIF, WebP, TIFF), text, CSV, JSON, XML, ZIP and Office documents.
Imports
Body types are set automatically when you import:- OpenAPI 3.x:
multipart/form-databecomes a multipart form (properties withformat: binary,format: base64orcontentMediaTypebecome file fields;encoding.contentTypeis used per part),application/x-www-form-urlencodeda URL-encoded form,application/octet-streamand image/PDF types a binary body, and XML/text a raw body. - Swagger 2.0:
in: formDataparameters become form fields;type: fileparameters become file fields. - Postman: form-data, URL-encoded, raw XML/text and file bodies keep their type. The files themselves are not part of a Postman export, so file fields show Select <file name> until you pick a file.
Self-hosted installations
Files are stored on a volume (quixa-files, mounted at /app/data/files) by default. To use Azure Blob Storage instead, set: