I figured the problem and fixed it. There were 2 issues: (1) The accountId in the URL has a hyphen, like it should be, but the ACCOUNTID in the soap header has and should be an underscore. (2) Postman should set the SOAPAction to "get" in the request header (3) The "NetSuitePort" in the URL is case-sensitive. It seems its…

Hi @Richard James Uri-Oracle, I've already tried setting the SOAPAction in the request header in Postman to an empty string. I've tried various combinations of "get", "post", and with the entire namespace such as "urn:messages_2017_2.platform.webservices.netsuite.com#get",…

hi @Richard James Uri-Oracle At this time my struggle is getting Postman to submit the soap request to the Netsuite webservice. I believe I have the signature part worked out, but first I need to get past the error around SOAPAction header.

The paymentMethod, and Credit Card number/cvv are working with the Netsuite SOAP interface, just not with the REST API. I wish someone from the REST team would look into my question and guide me in the right direction. Thanks!

Update: I figured I can look for the newly generated SalesOrderId from the response by looking at the Location parameter in the Header. I then figured I could run the following post requests https://99990-sb1.suitetalk.api.netsuite.com/services/rest/record/v1/salesOrder/{id}/!transform/itemFulfillment and…