NetSuite Token-Based Authentication Setup for Unified

Unified connects to NetSuite using Token-Based Authentication (TBA), requiring five key values: Realm/Account ID, Consumer Key, Consumer Secret, Token ID, and Token Secret. The setup process involves enabling TBA and REST Web Services in NetSuite's features, identifying the Realm ID, creating an integration record to generate the Consumer Key and Secret, and configuring the role used for the token to avoid login and permission issues. Using the Administrator role is recommended for simplicity, but a custom role with specific permissions can be created for security reasons. The role must have access to all necessary subsidiaries, and tokens are created for a combination of User, Role, and Integration Record. The access token's permissions are determined by the selected role, and it's crucial to provide the correct information to Unified to ensure successful API interactions. Validation issues, such as a 401 INVALID_LOGIN error, often arise from using the wrong role, token, or account ID, and can be resolved by reviewing the Login Audit Trail and ensuring tokens match their respective environments.