Sorry for the delay, I'll work on getting that to you as soon as I can but I'm not sure JSON is the culprit, unless there is some very odd specific minor difference when using Invoke Web Service.
I did manage to make a workaround using Powershell to make the API call instead, but aside from the difference in formatting that Powershell requires vs. Power Automate Desktop, I truly can't find any reason it shouldn't work in PAD.
JSON Body example:
{"policyNumber":"CP4000057J","companyCode":"LM1","pendingIndicator":"Y","callType":"1","error":"","premium":{},"agreementId":89004026}
Here is all of the input used that would never generate a proper result for me. Most often the API would come back with an error that indicated it had an issue with the policy number that was passed, either not reading it correctly or a format issue or something but it is set right in the variable and even when typing out everything manually (not using variables) it still gave this error.
I know the POST call works, as using the exact same URL, ApiKey header, and body as used above, it works absolutely find in Postman and gives a proper response.
I was able to get it working with a rigged together fix, but I really would like to get the built-in Invoke Web Service function to work for it as I really don't understand what issue it is having.
Powershell's Invoke-RestMethod but it's just some extra steps of having to create a local powershell script to do the API call, get the results, write that to a file, convert from Base64, etc, etc, and go from there. The format of how Invoke-RestMethod wants the data input is slightly different, but otherwise the variables and data within it are passed through the same way:
Did I just find a random needle in the haystack bug or something? I would be inclined to think the API itself is the issue, but ONLY attempting the Post from the PAD Invoke Web Service activity results in failure. My best guess is that the Invoke Web Service PAD utility is somehow slightly manipulating the boyd contents as they are being sent and that is what is causing it to fault.
I'm all ears if anyone has any ideas to try with the built-in PAD method... or even if you know of a more efficient method that is not that way at this point. This powershell way works and it will do if it's the only option, but I'd just really like to use the built in feature if I can...
Thanks for any and all assistance!
