Setting up Token Based Authentication in NetSuite
Last updated: November 10, 2025
How to Generate a NetSuite Token for the Integration
Follow these steps in NetSuite and then prepare the four resulting values (Consumer Key, Consumer Secret, Token ID, Token Secret) to use in authentication with Net Suite.
⚠ You must have a NetSuite role with permissions to manage integrations and tokens (typically an Administrator or a role with the Access Token Management / User Access Tokens permissions).Oracle Documentation+1
Step 1 – Log in to the correct NetSuite account
Log in to NetSuite in your browser.
Make sure you’re in the correct account (Production vs Sandbox) that you want the integration to use.
Note: Tokens are per account (production tokens don’t carry over to sandbox and vice versa).Oracle Documentation+1
Step 2 – Ensure Token-based Authentication is enabled (one-time setup)
If this was already done for other integrations, you can skip this step.
Go to:
Setup → Company → Enable Features.Open the SuiteCloud tab.
In the Manage Authentication section, make sure Token-based Authentication is checked.
Click Save if you changed anything.Oracle Documentation+1
Step 3 – Create / identify the Integration record (Consumer Key & Secret)
If you already have an Integration record for this integration, you can reuse it. Otherwise, create a new one.
Go to:
Setup → Integration → Manage Integrations → New.Oracle DocumentationEnter a Name (for example:
Employee API Integrationor our product name).Make sure State is Enabled.
On the Authentication section/tab, ensure Token-based Authentication is checked.
Save the record.
After saving, NetSuite will show you:
Consumer Key
Consumer Secret
👉 Important: These two values are shown only once.
Please copy and store them immediately (e.g. in a password manager) and then share them with us securely.Oracle Documentation+1
Step 4 – Make sure your role has token permissions
The role you’ll use to generate the token must:
Have token permissions (e.g. User Access Tokens or Access Token Management).Oracle Documentation+1
Have the necessary access to the data we need (e.g. Employees list permission if we’re reading employees).
If you’re unsure how to do this, an Administrator can:
Go to Setup → Users/Roles → User Management → Manage Roles.
Edit the role you use.
On Permissions → Setup, add:
User Access Tokens (for creating tokens for yourself), and/or
Access Token Management (for managing tokens for others).Oracle Documentation+1
On Permissions → Lists, ensure you have the required record permissions (e.g. Employees).
Step 5 – Create the Access Token (Token ID & Token Secret)
Now you’ll create the actual token tied to:
the Integration record (Step 3),
your User, and
your Role.
You can do this two ways; either is fine.
Option A – Using “Manage Access Tokens” (common for non-admins)
Log in as the user/role that will own the token.
In your Home dashboard, find the Settings portlet.
Click Manage Access Tokens.Oracle Documentation+1
Click New My Access Token.
On the Access Token page:
Application Name: select the Integration you created in Step 3.
The Token Name will auto-fill; you may rename it if you want.
Click Save.
Option B – Using the Setup menu (for admins)
Go to:
Setup → Users/Roles → Access Tokens → New.Oracle Documentation+1On the Access Token page, select:
Application Name: your Integration record from Step 3.
User: the user who will “own” the token.
Role: the role you prepared in Step 4.
Click Save.
After saving, NetSuite will display:
Token ID
Token Secret
👉 Important: These two values are also shown only once.
Copy them right away and store them securely.Oracle Documentation+1
Step 6 – Store the following values for use with YeshID
Once you’re done, you should have:
Consumer Key
Consumer Secret
Token ID
Token Secret
Contact us when you have these details to move forward.