Handling mtom attachments in Postman

[aviation-pilot-93951 (Jeroen)]

I’m testing a SOAP endpoint that returns a structured XML response with one or more PDFs, using MTOM. In the response, I see one or more xop:Include elements like this:

<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:0345bf1f-ed3f-4aa5-81b9-b4ac54e2d916-30@schemas.test.nl"/>

Further in the response, I find the binary encoding of the PDF:

Content-Type: application/pdf
Content-Transfer-Encoding: binary
Content-ID: <0345bf1f-ed3f-4aa5-81b9-b4ac54e2d916-30@schemas.test.nl>
Content-Disposition: attachment; name="asd-rene.pdf"
....

What can I do in Postman to download this PDF directly? Copying the binary content and converting it to a PDF with another tool is inconvenient, especially when there are multiple PDFs in the response.

[michaelderekjones (Mike Jones)]

Nothing that I’m aware of.

Postman is an API testing and development tool and that API is returning a binary encoding.

Converting it back to a PDF isn’t available within Postman (as far as I’m aware).

Postman has very little access to the local file system, so I don’t think there is anything you can do with the core apps.

You can however use Newman as Node.JS library, which means you might be able to do this as a Node.JS application alongside other libraries for file manipulation if its a really important.

[aviation-pilot-93951 (Jeroen)]

Thanks @michaelderekjones for the reply.