Requirements for Using an Application ID and User Credentials
If you want your request to authenticate by using user credentials, and you want to track the application by using a specific integration record, the following must be true:
-
An integration record for the application must exist at Setup > Integration > Manage Integrations. On the integration record, the User Credentials option must be enabled. For help creating an integration record, see Creating an Integration Record.
-
Your request must include, either explicitly or implicitly, the application ID that was generated when the integration record was created. If the integration was created in your NetSuite account, you can view the application ID on the integration record. If the integration record was created by a partner, in most cases you will obtain an updated integration from the partner that includes the application ID. With request-level credentials, the application ID must be included in the header of each request. For the login or ssoLogin request, you have an additional option, as described in Using Application ID with the Login and ssoLogin Operations.
The request must use a Passport object, not a TokenPassport. For examples of how to include Passport data in a request, see Authentication for SOAP Web Services.
Note that you can use either request-level credentials or the login operation. You can use any supported WSDL. NetSuite supports WSDLs for three years. For more details about WSDL support, see Support for Existing WSDL Versions.
As of the 2020.2 SOAP web services endpoint, authentication through request-level credentials is not supported. The Passport complex type is not supported. If you attempt to authenticate through request-level credentials in SOAP web services 2020.2 and later endpoints, the web services request is not processed, and an error message is returned. You must ensure that SOAP web services integrations created with 2020.2 and later SOAP web services endpoints use TBA. Authentication through user credentials continues to be supported in integrations that use SOAP web services 2020.1 and earlier endpoints. For more information, see Token-based Authentication and Web Services.