Hi, I've been accessing your API via PowerShell and everything has gone pretty smooth up to this point. However, now I'm trying to write a script that is able to send a fax with an attachment and I'm having issues with submitting the fax job if it has an attachment. The only type of attachment I have been able to send up to this point is plain text document, but I'd like to be able to send a PDF.
I'm currently sending using the multipart/mixed format. I tried to mimic the format that is in your API Reference page for createFaxMessage where the content-type is set as "multipart/form-data" and transmit the file in base64 encoded format, but at best I get the base64 data as plain text after the cover page.
Here is a copy of the message body as I'm sending it over. I've also set the content type as application/pdf which does not change the results: https://pastebin.com/phB61jy4
If the Base64 text is very small then the fax will deliver with the second page containing the base64 in plain text format. If the Base64 isn't very small (like the sample pdf in my pastebin which is 26kb), then I won't receive the fax at all. If I run a MessageStore API request a few minutes later, I see the status of the message updated to indicate messageStatus=SendingFailed; faxErrorCode=RenderingFailed
Is there a way to structure the message body so that your API recognizes the file as a PDF and decodes it properly? Since I'm using PowerShell to do this I'm unable to use your pre-packaged API, but up to this point it hasn't been a problem. If only I knew what your traffic API processor was looking for, I could probably shape the traffic so that it would work without issue.