The XML-based application programming interface (API) of the SOAP web services platform enables you to programmatically access your NetSuite data and business processes. Using SOAP web services, you need to have a header element that offers a flexible framework for specifying additional application-level requirements.
Scenario:
User wants to use a SOAP Web Services but doesn’t know how to setup a header.
Solution:
1. Set Account Number you will be using
2. Set Consumer Key.
Note: It is the generated key in the Integration Record creation once saved. See Discussion for creating Integration Record
3. Set Token ID.
Note: It is the generated token in the Access Tokens Record creation once saved. See Discussion for creating Access Token Record
4. Set Signature.
Note: The signature parameter is a base64 value of the HMAC-SHA, where the message is Base String and the value of the key parameter is the key.
The creation of the Base String is straightforward. Use percent encoding.
Parameters include: realm (accountID, also called scompid), consumer key, token key, nonce, and timestamp, with the ampersand character (&) as the delimiter. See SuiteAnswers Article for guidance. 77576 The Signature for Web Services and RESTlets
Here’s the sample Header in XML Format.
Here’s the SuiteAnswers Articles for more details.