Is it possible to build a web api in Appian to receive documents through multipart/form-data as body?In my case appian is adding following metadata and making the file unreadable(corrupt)
--TnQmfygKfP801A_kE1bGL-7YAFk_k6gl9 Content-Disposition: form-data; name="file"; filename="Profile Picture.jpg" Content-Type: image/png Content-Transfer-Encoding: binary
Discussion posts and replies are publicly visible
As far as I know, you're likely going to need to stick to one of the standard ways of receiving files over API as recommended by Appian in certain given recipes (I think the standard is Base64 where the document is the body of the message). There may be some wiggle room and some alternative ways to go about it, but I don't know how many alternatives there are where there's a guarantee that it'll cooperate with the required elements within Appian.
What are your requirements / specific restrictions from your external system? If you can provide more specifics about your limitations, others here may have some more specific advice for you.
We’re developing an Appian application to replace an existing system, and one of our requirements is to replicate an existing REST API that accepts file uploads.
Specifically, we need to expose an Appian Web API that can receive a document and its related metadata in a multipart/form-data POST request — similar to the existing external API.
multipart/form-data