Unanswered

Http Post Request fails in Flow with error 404 but Succeeds in POSTMAN

(0) Share

Report

Posted on by Community Power Pla...

Hi guys,

I'm trying to call an API with the action POST. The API works from POSTMAN, however, once the exact body is an API is called from flow, it fails. We've called several other API from the same vendor but only this specific API fails.

Here's the json body for anyone interested. Really hoping for any advice.

{
 "PolicyType": "AdvancedWinApp",
 "Name": "Test NUS REST API Advanced Policy",
 "Action": "NormalRun",
 "Activation": {
 "Enabled": true,
 "DeactivateDate": {
 "Year": 2025,
 "Month": 5,
 "Day": 30,
 "Hours": 8,
 "Minutes": 40,
 "Seconds": 0
 }
 },
 "IncludeComputersInSet": [
 {
 "Id": "62c3bb1c-0203-44bc-a6e0-839849df4210"
 }
 ],
 "ExcludeComputersInSet": [],
 "IncludeComputerGroups": [],
 "ExcludeComputerGroups": [],
 "IncludeUsers": [
 {
 "UserName": "NUSSTF\\stavg"
 }
 ],
 "IncludeUserGroups": [],
 "IncludeADComputerGroups": [],
 "ExcludeADComputerGroups": [],
 "Applications": [
 {
 "Type": "EXE",
 "FileName": "Examplify_2.5.4_win.exe",
 "FileNameCompare": "Exactly",
 "Owner": "NUSSTF\\stavg"
 }
 ]
}

This is the response on POSTMAN which is ok.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

fchopo 8,003 Moderator on at

Like (0)

Report

Hello @Anonymous

Are you encoding the Authentication Header value (the content stored in the EPMAuth... variable)? Have a look at this post: SharePoint Administration: Microsoft Flow | HTTP Rest API | Invalid Client Secret error (sharepointmadeeasy.blogspot.com)

Hope it helps!

Ferran

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi Ferren,

I am not encoding the Authentication Header value in the EPMAuth.. variable. In fact, I have 2 previous API running before it that works just fine and is done the same way. It's funny because this API is the only one that throws a 404. And testing it in POSTMAN works totally fine.

Was this reply helpful? Yes No
_Luke_ 2 on at

Like (0)

Report

Was just having the same issue and came across this post. Mine was a very basic POST request that worked in Postman and not in Power Automate when constructed identically. Here's what I did to get it to work:

Go into Settings for the HTTP connector.

Then turn on "Suppress workflow headers"

Click Done, Save your workflow and test. Mine worked flawlessly after this change.

Was this reply helpful? Yes No