Differences between Postman HTTP Post Rest API and Logic App HTTP action?

Copper Contributor

I am tearing my hair out.....what little i have left.  I am migrating a simple postman api rest call to a stand alone logic app.  The post call only contains header parameters to make this action and it works perfectly within postman.  however when I move it to a logic app HTTP action and replicate the call it does something to the headers and it does not pass the info the same which will not create the record correctly. (it does process correctly but it changes the payload somehow}  The api call creates a linked website to the target record.  not sure what else is going on in the background but the same format is not being passed to my host application from azure.........anyone have any ideas?

 

the postman http payload is below

POST /target/oslc/os/wodoclinks/10/doclinks HTTP/1.1
Host: xxx.73.xxx.11:9080
apikey: xxxmykeyxxx
x-document-meta: URL/Attachments
slug: 1070
Content-location: https://techcommunity.microsoft.com
x-document-description: me like

 

The logic app runtime call comes out like this

{
    "method": "POST",
    "headers": {
        "Content-location": "https://techcommunity.microsoft.com",
        "apikey": "xxxmykeyxx",
        "slug": "1070",
        "x-document-description": "me like",
        "x-document-meta": "URL/Attachments"
    }
}

 

1 Reply
I would add an explicit host, content-type, and x-public-uri headers first. Most of the maximo APIs (I'm guessing since I see /oslc in your path) require content-type set to "application/json"
You should also try https.
If none of that works, try following the steps in https://www.ibm.com/support/pages/creating-and-using-rest-api-keys-secure-application-server-environ...
As a final step, contact IBM support