✅ Authorization
✅ 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
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ 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 | ✅ |
Bills
Credit Notes
Customers
Fields
Endpoint | Description | Readme |
---|---|---|
GET /fetch-fields | Fetches all fields in Netsuite | 🔗 |
Invoices
Payments
Purchase Orders
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
No setup guide yet.
restlets
, rest_webservices
and/or suite_analytics
)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 the netsuite-tba
integration in Nangonetsuite-tba
netsuite-tba
and leave the “Client Id” and “Client Secret” values empty.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.
The role must have the following permissions enabled under Setup > Users/Roles > Manage Roles > [Your Role] > Permissions:
Under “Setup”:
To create an access token for a non-admin role:
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.
Users who will be creating integrations and tokens need these additional permissions:
Under “Setup”:
If you need to make concurrent API calls:
The “Concurrent Web Services User” setting may require an additional user license. Consult your Netsuite account representative for details.
If you encounter authentication issues:
Permission Verification:
Role Configuration:
For detailed permission setup, refer to the Netsuite Token-Based Authentication Setup Guide.
✅ Authorization
✅ 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
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ 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 | ✅ |
Bills
Credit Notes
Customers
Fields
Endpoint | Description | Readme |
---|---|---|
GET /fetch-fields | Fetches all fields in Netsuite | 🔗 |
Invoices
Payments
Purchase Orders
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
No setup guide yet.
restlets
, rest_webservices
and/or suite_analytics
)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 the netsuite-tba
integration in Nangonetsuite-tba
netsuite-tba
and leave the “Client Id” and “Client Secret” values empty.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.
The role must have the following permissions enabled under Setup > Users/Roles > Manage Roles > [Your Role] > Permissions:
Under “Setup”:
To create an access token for a non-admin role:
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.
Users who will be creating integrations and tokens need these additional permissions:
Under “Setup”:
If you need to make concurrent API calls:
The “Concurrent Web Services User” setting may require an additional user license. Consult your Netsuite account representative for details.
If you encounter authentication issues:
Permission Verification:
Role Configuration:
For detailed permission setup, refer to the Netsuite Token-Based Authentication Setup Guide.