NetSuite is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Enter your NetSuite Account ID in the field above (from Setup → Company → Company Information → Account ID)
In NetSuite, go to Setup → Integration → Manage Integrations → New
Enable Token-Based Authentication
Save and note the Consumer Key and Secret
Go to Setup → Users/Roles → Access Tokens → New to create an access token
Paste your Consumer Key, Consumer Secret, Token ID, and Token Secret below
Ready to connect?
Go directly to the integrations page in your dashboard.
These are the data scopes On Belay can be granted for NetSuite. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
accounting:read | Read accounting data | Read only |
inventory:read | Read inventory | Read only |
orders:read | Read orders | Read only |
customers:read | Read customers | Read only |
financials:read | Read financials | Read only |
reports:read | Read reports | Read only |
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Some API keys have expiration policies. Generate a new key in NetSuite and update it in On Belay → Integrations → NetSuite → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →