Overview
To authenticate NetSuite, you will need to provide the following information:
Consumer Key
Consumer Secret
Token ID
Token Secret
This guide will walk you through finding or creating those credentials within NetSuite.
Prerequisites
Please ensure you fulfill all the requirements to set up the integration:
You have Administrator permissions in your company's NetSuite instance, or someone has shared their access with you.
Instructions
Step 1: Finding your NetSuite Account ID
Log into your NetSuite portal
Copy the subdomain of the URL at the top of your browser and enter it within Merge Link
Your NetSuite Account ID is the combination of letters or numbers before "app.netsuite.com"
For example, if your URL is "https://7600508.app.netsuite.com/app/center/card.nl?sc=-29&whence=", the value to input within Merge Link is 7600508
Step 2: Enable web services and token-based authentication
In your NetSuite account, go to Setup > Company > Enable Features or search Enable Features in the search bar
Under SuiteCloud, check the boxes next to SOAP WEB SERVICES and REST WEB SERVICES
Also under SuiteCloud, ensure the box next to TOKEN-BASED AUTHENTICATION is checked
Step 3: Import the setup bundle to create a role
In your NetSuite account, navigate to Customization > SuiteBundler > Search & Install Bundles or search Search & Install Bundles in the search bar
Search for and select one of the Merge Permissions Bundles
Note that there are two available bundles. The Merge Read-only Permissions Bundle will allow for read-only access, and the Merge Full Permissions Bundle will allow for read-and-write access
Select the Bundle that fits your use case and click Install
The bundle will begin installing. It may take up to 5 minutes to install and you may be re-routed to the Installed Bundles page when the installation is complete
The bundle creates a role that can authenticate to NetSuite's API. For a full list of the role's permissions, see this article. The permissions may be updated, or a separate Role may be used, but doing so could result in permission issues.
Step 4: Assign a user to the role
Navigate to Setup > Users/Roles > Manage Users or search Manage Users in the search bar
In the Manage Users page, either select a user to assign the Role to or create a new user
Most users use an existing user (often yourself) so that an additional NetSuite seat is not consumed
To create a new user, however, go to Lists > Employees > Employees > New. Create the user and grant them NetSuite access by going to the Access tab in the Employee record and select 'Give Access'
In the user's employee record, click Edit and go to the Access tab. In your Access tab, go to Roles and select the Role you imported through the Import Bundle process in Step 3
Click Save to apply these changes
Step 5: Create an integration to obtain your Consumer Key and Secret
Once the user and the role are set up, navigate to Setup > Integration > Manage Integrations > New
Create an integration with the below details:
Any value can be populated in the NAME field
The CONCURRENCY LIMIT should be left unpopulated
Ensure the REST WEB SERVICES box is checked under SCOPE
The TOKEN-BASED AUTHENTICATION and TBA AUTHORIZATION FLOW boxes should be checked
Fill in the CALLBACK URL and REDIRECT URI with a value of https://app.merge.dev/oauth/callback
Once the integration is saved, you will receive a Consumer Key and Consumer Secret (at the bottom of the confirmation screen). This will only be shown once, so keep them in a secure place
Step 6: Create an access token to obtain your Token ID and Secret
In your Setup tab, go to Users/Roles, Access Tokens, > New or search New Access Token in the search bar to begin creating a New Access Token
Ensure the below details are selected and click Save
Application Name: Name of the Integration created in Step 5
User: User that the Role was added to during Step 4
Role: The imported role (either Merge Full Permissions or Merge Read-only Permissions)
Copy the Token ID and Token Secret and store them in a safe place. They will only be shown once
Step 7: Enter credentials in the linking flow
