Netsuite TBA
Overview
Pre-built tooling
โ
Authorization
โ Authorization
โ
Read & write data
โ Read & write data
Tools | Status |
---|---|
Pre-built integrations | โ |
API unification | โ |
2-way sync | โ |
Webhooks from Nango on data modifications | โ |
Real-time webhooks from 3rd-party API | ๐ซ (time to contribute: <48h) |
Proxy requests | โ |
โ
Observability & data quality
โ Observability & data quality
Tools | Status |
---|---|
HTTP request logging | โ |
End-to-type type safety | โ |
Data runtime validation | โ |
OpenTelemetry export | โ |
Slack alerts on errors | โ |
Integration status API | โ |
โ
Customization
โ Customization
Tools | Status |
---|---|
Create or customize use-cases | โ |
Pre-configured pagination | ๐ซ (time to contribute: <48h) |
Pre-configured rate-limit handling | ๐ซ (time to contribute: <48h) |
Per-customer configurations | โ |
Pre-built integrations
Bills
Bills
Credit Notes
Credit Notes
Customers
Customers
Fields
Fields
Endpoint | Description | Readme |
---|---|---|
GET /fetch-fields | Fetches all fields in Netsuite | ๐ |
Invoices
Invoices
Payments
Payments
Purchase Orders
Purchase Orders
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | โ | |
Paid test account | โ | |
Partnership | โ | |
App review | โ | |
Security audit | โ |
Setup guide
No setup guide yet.
Useful links
- How to register an Application
- OAuth-related docs
- Scopes (
restlets
,rest_webservices
and/orsuite_analytics
) - API endpoints
Connection configuration in Nango
- Netsuite requires a user specific account id to run OAuth.
API gotchas
- There doesnโt seem to be a way to create a Netsuite account without scheduling a call.
- The
netsuite
integration which uses OAuth 2.0 has a refresh token that has a fixed expiration of 7 days. After which point the refresh token becomes invalid and a new access token must be obtained by making users go through the authorization code flow again. To avoid this we recommend using the machine to machine flow which is called thenetsuite-tba
integration in Nango
Admin Setup for netsuite-tba
- Ensure you have admin privileges and login to your Netsuite account and navigate to Setup > Company > Enable Features
- Under the โSuiteTalkโ header make sure the SOAP WEB SERVICES and REST WEB SERVICES checkboxes are checked
- Under the โManage Authenticationโ header make sure the TOKEN-BASED AUTHENTICATION checkbox is checked
- Click the save button
- Navigate to Setup > Integration > Manage Integrations > New
- Set the desired name of this integration
- Enable TOKEN-BASED AUTHENTICATION and disable TBA: AUTHORIZATION FLOW and AUTHORIZATION CODE GRANT
- Click the save button
- The client credentials will now be displayed and be sure to copy the Consumer Key, Client ID, Consumer Secret, and Client Secret
- Navigate to the homepage by clicking the home icon
- At the button left corner click the Manage Access Tokens button
- Select the Application Name you created for this integration
- Enter a โToken Nameโ
- Save your new access token
- The token credentials will now be displayed. Copy the โToken IDโ & โToken Secretโ
- In Nango create a new integration using the
netsuite-tba
and leave the โClient Idโ and โClient Secretโ values empty. - Create a new connection and for the โOAuth Client Id Overrideโ value paste in the value you received from Netsuite called โClient IDโ and for the โOAuth Client Secretโ value paste in the value you received from Netsuite called โClient Secretโ. For โToken IDโ & โToken Secretโ paste in the values you received from Netsuite from the access token step. The account ID value can be found from your Netsuite URL instance
Non-Admin Role Setup for netsuite-tba
When setting up Netsuite TBA with a non-admin role, additional configuration is required. This section covers the necessary permissions and setup steps for non-administrator users.
Required Role Permissions
The role must have the following permissions enabled under Setup > Users/Roles > Manage Roles > [Your Role] > Permissions:
Under โSetupโ:
- SOAP Web Services permission
- REST Web Services permission
- Token-Based Authentication permission
- OAuth 2.0 permission (recommended for future flexibility)
Creating Access Tokens with Specific Roles
To create an access token for a non-admin role:
- Switch to the desired role using the role selector in the top-right corner
- Navigate to Setup > Integration > Manage Access Tokens
- Click โNew Access Tokenโ
- Select your application from the dropdown
- Provide a token name
- Save and securely store the Token ID and Token Secret that are displayed
The role selection at token creation time determines the permissions available to that token. Make sure youโre using the correct role before creating the token.
Required Permissions for Token Management
Users who will be creating integrations and tokens need these additional permissions:
Under โSetupโ:
- Access Token Management permission
- Integration Application permission
- Manage Integration permission
Additional Configuration Considerations
Concurrent Web Services User
If you need to make concurrent API calls:
- Navigate to Setup > Company > Enable Features > SuiteCloud tab
- Enable โCONCURRENT USERS FOR WEB SERVICESโ
- For each user that needs this capability:
- Go to Setup > Users/Roles > Manage Users
- Edit the user
- Check โWeb Services Userโ
- Check โConcurrent Web Services Userโ
The โConcurrent Web Services Userโ setting may require an additional user license. Consult your Netsuite account representative for details.
Troubleshooting Non-Admin Access
If you encounter authentication issues:
-
Permission Verification:
- Log out and log back in after permission changes
- Verify permissions are saved by checking the role again
- Ensure all parent permissions are also enabled (some permissions have dependencies)
-
Role Configuration:
- Confirm the user is assigned the correct role
- Verify the role has all required permissions listed above
- Check if the role has access to the necessary records and features
For detailed permission setup, refer to the Netsuite Token-Based Authentication Setup Guide.