cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JonathanM
Frequent Visitor

HTTP Post multipart/form-data

Hi,

 

I am trying to post SharePoint files to a 3rd party via their API.  Their API uses multipart/form-data.  After some trial and error, I can POSTcontent, but only text files come out correctly on the destination.  Other files (Excel, Word, jpg, etc.) post, but the data is not readable. What do I need to do to the file content to format it properly?

 

Thanks!

 

http post.png

 

51 REPLIES 51
v-yuazh-msft
Community Support
Community Support

Hi @JonathanM,

 

The file content is with type base 64 when the files with type Excel, Word, jpg, etc.

 

Best regards,

Alice

Thanks Alice.  I've tried converting the content a variety of ways, but have not been able to get it converted properly.  What should the formula be to convert the file content?

 

Thanks,

 

Jonathan

Anonymous
Not applicable

@JonathanM Did you ever resolve this issue?

How were you able to post text files using this method in the first place? Everthing I try just converts the whole string to base64 and flow completely ignores the multipart sections.

I'm trying to do it now through swagger but still no luck yet.

Any updates you have here would be much appreciated.

 

Thanks,

Sam

Hi @Anonymous 

 

This worked for me for any type of content (text, Word, Excel, etc.)

2019-04-02_08h15_42.png

Anonymous
Not applicable

@JonathanM Thanks for this.

Unfortunately it's not working for me. I'm posting to the API for Atlassian Jira Cloud.

It responds with a code of 200 but no file is actually created.

 

2019-04-02_1817.png

Anonymous
Not applicable

I got it working in the end. I had to specifically define the content type in the body

Screenshot 2019-04-02 at 22.10.53.png

@JonathanMor @Anonymous  Do you know how to modify the request body to include other parameters in the multi-part form? Your examples appear just to have a single part, which is the file itself.

Anonymous
Not applicable

@WillPage  What else are you trying to update?

 

Also are you able to make the call you wish from Postman? I used postman calls to a test flow I built to figure out the structure I needed. Perhaps you can do the same. If you have an example of the postman call then screenshot it here as well if you can.

@Anonymous  Thanks for responding.

 

It's a file upload to Bamboo HR. They need a bit of metadata with the file; a category, which is basically the folder it goes in and whether it's shared or not. Here's their doco https://www.bamboohr.com/api/documentation/employees.php#uploadEmployeeFile

 

It works fine in Postman, and it works fine posting plain text in the file content using the example copy-pasted in the documentation (with the category changed).

 

I've tried using your example and adding the metatdata as extra records in the $multipart object like this

 

{
  "$content-type": "multipart/form-data",
  "$multipart": [
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"category\""
      },
      "body": {
        "$content": "18"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"fileName\""
      },
      "body": {
        "$content": "test.bmp"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"share\""
      },
      "body": {
        "$content": "yes"
      }
    },
    {
      "headers:": {
        "Content-Disposition": "form-data; name = \"file\"; filename=\"test.bmp\""
      },
      "body": {
        "$content-type": "application/octet-stream",
        "$content": {
          "$content-type": "image/bmp",
          "$content": "iVBORw0KGgoAAA............Jggg=="
        }
      }
    }
  ]
}

However, I get 403 Forbidden back from the server. File category 18 is the only one I have write access to, so there's every chance the metadata isn't being sent properly and it's denying me to write whatever the default file category is.

 

Here's the screen shot from Postman:Capture.PNG

 

What I pasted as the request body there was copied from the output of a failed run. I spotted that Flow is adding its own record for the body... However, it still fails with a 403:

 

Request body as seen in the designer:

{
  "$content-type": "multipart/form-data",
  "$multipart": [
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"category\""
      },
      "body": {
        "$content": "18"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"fileName\""
      },
      "body": {
        "$content": "test.bmp"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"share\""
      },
      "body": {
        "$content": "yes"
      }
    },
    {
      "headers:": {
        "Content-Disposition": "form-data; name = \"file\"; filename=\"test.bmp\""
      },
      "body":  @{body('Get_file_content_using_path')}
      
    }
  ]
}

And as seen in the output of a failed run:

 

{
  "$content-type": "multipart/form-data",
  "$multipart": [
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"category\""
      },
      "body": {
        "$content": "18"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"fileName\""
      },
      "body": {
        "$content": "test.bmp"
      }
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"share\""
      },
      "body": {
        "$content": "yes"
      }
    },
    {
      "headers:": {
        "Content-Disposition": "form-data; name = \"file\"; filename=\"test.bmp\""
      },
      "body": {
        "$content-type": "image/bmp",
        "$content": "iVBORw.................Jggg=="
      }
    }
  ]
}
Anonymous
Not applicable

@WillPage  Sorry for the late reply.

 

1) Does your postman flow work?

2) Assuming it does work, change the endpoint of the postman flow to a new flow just with an HTTP request trigger (add just a compose or something so you can save it. Then run it once and open the log of the flow that ran then copy the body received by the HTTP trigger here. If one of the items youve posted above is already this then let me know which one.

 

Sam

@AnonymousNow that I've done that it's clear why it isn't working.

 

This is the body of the request coming from Postman, as captured by a flow with HTTP trigger:

 

----------------------------633613363255592221149085
Content-Disposition: form-data; name="category"

18
----------------------------633613363255592221149085
Content-Disposition: form-data; name="fileName"

Will Page - Signed Induction.pdf
----------------------------633613363255592221149085
Content-Disposition: form-data; name="share"

yes
----------------------------633613363255592221149085
Content-Disposition: form-data; name="file"; filename="Will Page - Signed Induction.pdf"
Content-Type: application/pdf

%PDF-1.7
... Rest of PDF file.

 

 

..and this is from Flow:

 

--cbd9b14e-6955-43e3-a757-c4e5d1d3d3c3
Content-Type: application/json; charset=utf-8
Content-Disposition: form-data; name="category"

{"$content":"18"}
--cbd9b14e-6955-43e3-a757-c4e5d1d3d3c3
Content-Type: application/json; charset=utf-8
Content-Disposition: form-data; name="fileName"

{"$content":"Will Page - Signed Induction.pdf"}
--cbd9b14e-6955-43e3-a757-c4e5d1d3d3c3
Content-Type: application/json; charset=utf-8
Content-Disposition: form-data; name="share"

{"$content":"yes"}
--cbd9b14e-6955-43e3-a757-c4e5d1d3d3c3
content-type: application/pdf

%PDF-1.7
... Rest of PDF file

 

 

I do note that the file content is not corrupt. It looks the same as the original in a text editor at least, which is more than can be said when adding dynamic content from a Get file content action directly into a plain text request body, (like the output from Postman above or the example on the Bamboo HR documentation).

 

Now, if I can define the multipart boundaries using JSON, and the file content but have the metadata as plain text this would work. Is that possible, or am I going to have to do this in an Azure Function?

So, this body:

 

{
  "$content-type": "multipart/form-data",
  "$multipart": [
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"category\""
      },
      "body": "18"
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"fileName\""
      },
      "body": "Will Page - Signed Induction.pdf"
  
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"share\""
      },
      "body": "yes"
    },
    {
      "headers:": {
        "Content-Disposition": "form-data; name=\"file\"; filename=\"Will Page - Signed Induction.pdf\""
      },
      "body": @{body('Get_file_content')}
    }
  ]
}

Gives me this output:

--3b77c044-c94c-4156-8322-01ca7e812bcb
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name="category"

18
--3b77c044-c94c-4156-8322-01ca7e812bcb
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name="fileName"

Will Page - Signed Induction.pdf
--3b77c044-c94c-4156-8322-01ca7e812bcb
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name="share"

yes
--3b77c044-c94c-4156-8322-01ca7e812bcb
content-type: application/pdf

%PDF-1.7

...which looks OK apart from the Content-Type header I didn't ask for in each section. Unfortunately though, The Bamboo HR API gives me a 400 error when I send it this. Guess I'm stuck!

This is the error coming back from the Bamboo HR API now....

Capture.PNG

It's just clicked. For some reason the last part:

 

 {
      "headers:": {
        "Content-Disposition": "form-data; name=\"file\"; filename=\"Will Page - Signed Induction.pdf\"",
"Content-Type": "application/pdf"
      },
      "body": @{body('Get_file_content')}
    }

When run through the Flow comes out without the Content-Disposition attached:

--4a6c27da-af8b-479d-af08-824f21977c40
content-type: application/pdf

%PDF-1.7
..Rest of PDF

--4a6c27da-af8b-479d-af08-824f21977c40

..so close but not quite there!

@AnonymousThanks so much for your help. I finally figured this out:

 

{
  "$content-type": "multipart/form-data",
  "$multipart": [
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"category\""
      },
      "body": "18"
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"fileName\""
      },
      "body": "Will Page - Signed Induction.pdf"
    },
    {
      "headers": {
        "Content-Disposition": "form-data; name=\"share\""
      },
      "body": "yes"
    },
    {
      "headers": {
"Content-Disposition": "form-data; name=\"file\"; filename=\"Will Page - Signed Induction.pdf\""},
      "body": {
"$content-type": "application/pdf",
"$content": "@{base64(body('Get_file_content'))}"
}
    }
  ]
}

Without your tip of creating a Flow to capture and debug the output I'd have spent a million years on this - having that info was crucial.

 

The last part was simply to convert the output of Get file content to Base64 rather than feed the raw content straight into the Flow and let it infer the content type and create an object out of it.

 

So happy to see this working!

Anonymous
Not applicable

@WillPage So happy to see you've got it working! 

Glad to be of service.

davidlist87
Advocate I
Advocate I

Hi Guys,

 

I was wondering if you could help with my problem.

 

I am try to POST an image to a machine learning service but I'm getting a weird error back.

JPG is one of the only content types allowable. I have tested this using Postman multipart/form-data but I am struggling to POST is using raw JSON.

Image 1.jpgImage 3.jpg

 

You need to show us the body of your HTTP request and the error message, to be in with any chance of getting help.

Helpful resources

Announcements

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Our team will be reviewing posts using the new "Copilot Studio" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!    

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Did You Attend the Microsoft Power Platform Conference in 2022 or 2023? Claim Your Badge Today!

If you were one of the thousands of people who joined us at the first #MPPC Microsoft Power Platform Conference in 2022 in Orlando--or attended the second-annual conference in Las Vegas in 2023--we are excited to honor you with a special community badge! Show your support for #MPPC Microsoft Power Platform Conference this year by claiming your badge!           Just follow this link to claim your badge for attending #MPPC in 2022 and/or 2023: MPPCBadgeRequest    Want to earn your badge for 2024? Just keep watching our News & Announcements for the latest updates on #MPPC24.

Microsoft Power Platform | 2024 Release Wave 1 Plan

Check out the latest Microsoft Power Platform release plans for 2024!   We have a whole host of exciting new features to help you be more productive, enhance delegation, run automated testing, build responsive pages, and so much more.    Click the links below to see not only our forthcoming releases, but to also try out some of the new features that have recently been released to market across:     Power Apps  Power Automate  Copilot Studio   We can’t wait to share with you all the upcoming releases that will help take your Power Platform experience to the next level!    Check out the entire Release Wave: Power Platform Complete Release Planner 

Users online (4,237)