Integration Record Overview

The integration record helps you manage and monitor SOAP web services requests to your NetSuite account. This is especially useful if you have multiple apps sending requests. For example, your sales team uses one app to send new customer data. Your HR team uses a different app to update employee records. Each application can be represented by its own integration record.

For more details, see the following sections:

Benefits of the Integration Record

You can do the following when using integration records for your external apps:

Application IDs

Every integration record has a unique application ID. The ID is a 32-character unique identifier generated when you create the record. You can find the ID in the Application ID field on the integration record. Application IDs are only visible in the account where they were created. When a partner distributes an integration record, their customers can't see the application ID in their own accounts.

You need to include an application ID in some SOAP web services requests. If you're using token-based authentication, leave out the application ID.

Use the following guidelines:

Treat application IDs as confidential, even though they're not authentication credentials.

Endpoint Requirements

Integration records work with any supported endpoint. Requirements vary depending on the endpoint you use.

2015.1 and Earlier

Note the following if you're using the 2015.1 endpoint or earlier:

2015.2 and Later

When you upgrade to 2015.2 or later, associate SOAP requests with a non-default integration record. Each request needs one of the following:

Note:

There's one SOAP web services operation that doesn't need authentication or app identification. It is the getDataCenterUrls.

2016.2 and Later

NetSuite 2016.2 introduces two new permissions for non-administrator users to view and manage integration records.

The Integration Applications permission (List type) lets users view the Integrations list page.

The Integration Application permission (Full level, Setup type) allows users to view, edit, and create integration records. This permission also gives access to the Integration field in SOAP Web Services Operations search.

For details about SOAP web services searches, Searching for SOAP Web Services Log Information.

Ownership of Integration Records

Creating an integration record makes it instantly available in your NetSuite account. Your NetSuite account owns the record, and administrators can edit it freely.

You can also install records from other sources in your account:

Important:

As of 2019.1, when calling the Issue Token endpoint, an Integration record is created and automatically installed in your account. TThe Require Approval preference controls whether the new record is enabled automatically. You can manage the preference at Setup > Integration > Integration Management > SOAP Web Services Preferences. If the Require Approval box is unchecked (set to false), the new application's State is set to Enabled, allowing all requests. If the box is checked (set to true), the State is set to Waiting for Approval. Then, you need to manually enable the record. Until you set the state to Enabled, all requests sent by that application are blocked.

Records that are installed through either of these methods aren't fully editable, because they are considered to be owned by a different NetSuite account. You can only edit the Note and State fields on these records. Other fields can only be changed by the owner account's authorized users, including the permitted authentication options and the Description field. Changes made by the owner are automatically synced to your account. These changes won't appear in your account's system notes.

For more information about creating integration records, see Creating an Integration Record. For more details about distributing integration records, see Distributing Integration Records.

Related Topics

General Notices