Can't get encrypted email message body sent via API in correct format

  • 1
  • Problem
  • Updated 2 months ago
Message files used for encrypted emails over API do not display in proper format. If there is a way to specify file type (MIME, e.g., plain/text, html, etc.), it is not documented in the API. Files upload fine and recipient receives notification okay, but when opening the message, they see something like:

--------------------------53cdb1dd93d911ee
Content-Disposition: form-data; name="temp.txt"; filename="temp.txt"
Content-Type: application/octet-stream Our patient John Doe 11-15-1997 has successfully registered --------------------------53cdb1dd93d911ee--

I really need some help to solve this problem.
Photo of Robert Clark

Robert Clark

  • 3 Posts
  • 0 Reply Likes
  • Frustrated to the point of seeking a ShareFile alternative

Posted 2 months ago

  • 1

Be the first to post a reply!