Requirements for Using an Application ID and User Credentials
To authenticate with user credentials and track an app with an integration record, follow these requirements:
-
An integration record for the application must exist at Setup > Integration > Manage Integrations. The User Credentials option must be enabled on the integration record. For help creating an integration record, see Creating an Integration Record.
-
Your request must include the application ID generated when the integration record was created. If you created the integration in your NetSuite account, you can view the application ID on the integration record. IIf a partner created the integration, you'll usually get an updated version with the application ID from them. With request-level credentials, include the application ID in each request's header. For the login or ssoLogin request, you have an additional option, as described in Using Application ID with the Login and ssoLogin Operations.
Use a Passport object, not a TokenPassport, in your request. 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.
Starting with the 2020.2 SOAP web services endpoint, request-level credentials are no longer supported for authentication. The Passport complex type isn't supported. Attempting to use request-level credentials in 2020.2 and later endpoints will result in an error and the request won't be processed. For 2020.2 and later endpoints, ensure your SOAP web services integrations use TBA. User credential authentication is still supported in 2020.1 and earlier endpoints. For more information, see Token-based Authentication and Web Services.