Identify the Target OAuth 2.0 Approach per Integration

For each integration currently using TBA, choose the OAuth 2.0 flow that fits the purpose of the integration:

• OAuth 2.0 client credentials flow (machine-to-machine)

  Ideal for background services and server-side workloads that don't require a user to log in and interact with them.

• OAuth 2.0 authorization code grant flow (user-authorized)

  Ideal for integrations that require a user to grant access to the application.

If you use third-party integrations in your NetSuite account, ensure that they are configured to use OAuth 2.0 before the TBA end of support.

Related Topics

• Getting Started with Token-based Authentication
• Manage TBA Tokens in the NetSuite UI
• Using the TBA Access Token Search Page
• Create Integration Records for Applications to Use TBA
• Getting Started with OAuth 2.0
• Managing OAuth 2.0 Authorized Applications
• Create Integration Records for Applications to Use OAuth 2.0
• OAuth 2.0 Client Credentials Setup
• OAuth 2.0 for Integration Application Developers

General Notices