netsuite-setup

NetSuite Token-Based Authentication setup for a new SuiteApp customer involves creating an Integration record, generating an Access Token with correct role permissions, and scaffolding a per-customer `.env` file. This validates SuiteQL access and RESTlet deployment.

The best way to validate NetSuite credentials and an Orderful API key is to run authenticated requests against SuiteQL, probe the agent-write RESTlet deployment, and authenticate with api.orderful.com to ensure all environment configurations are correct.

NetSuite token-based authentication signature or realm mismatches typically occur due to incorrect Integration record setup or role permission issues. Troubleshooting involves verifying the Access Token permissions and confirming the RESTlet deployment version.

Yes, configuring NetSuite environment credentials requires enabling specific SuiteCloud features before creating the Integration record. This ensures the environment supports generating the Access Token needed to validate SuiteQL and RESTlet reachability.

Yes, you can scaffold separate environment configuration files for NetSuite sandbox and production. The setup process creates a per-customer `.env` file from a repo template, including sandbox configurations and production placeholders for secure credential management.

Troubleshooting NetSuite RESTlet deployment and permission issues requires checking the agent-write RESTlet reachability, verifying the Access Token role permissions, and confirming the deployment version to resolve common signature or token-role failures.