Integrating NetSuite Inventory
Auth: OAuth 2.0 · Partner program: required · Setup time: about 40 minutes · Last verified: 2026-05-23
Oracle NetSuite is the enterprise reference SaaS ERP. The adapter targets the inventory surface of NetSuite REST Web Services — items (inventoryitem, assemblyitem, kititem), locations, inventoryitemlocations, inventorynumber, inventoryadjustment, and vendors — and maps them into the canonical inventory schema.
Auth model
Section titled “Auth model”- OAuth 2.0 Authorization Code grant (user-delegated): authorize at
https://{accountID}.app.netsuite.com/app/login/oauth2/authorize.nl. Exchange via POST tohttps://{accountID}.suitetalk.api.netsuite.com/services/rest/auth/oauth2/v1/token. - OAuth 2.0 Client Credentials grant (M2M): same token endpoint, signed JWT client assertion (RS256/ES256) using a certificate uploaded to the user mapped to the integration record. This is the standard pattern for headless SuiteApp installs.
- Access tokens expire after
3600seconds; refresh tokens last7days (Auth Code flow). Most production SuiteApps combine the flows — Auth Code once to upload the certificate, then Client Credentials for ongoing access. {accountID}is the customer’s NetSuite account id (e.g.1234567or1234567_SB1for a sandbox). Lowercase + underscores in the hostname; dashes are not valid.
Prerequisites
Section titled “Prerequisites”- A NetSuite account (production or sandbox / Release Preview). Inventory module + REST Web Services + OAuth 2.0 features must be enabled under Setup → Company → Enable Features.
- An Integration Record under Setup → Integration → Manage Integrations → New with OAuth 2.0 enabled and the desired grants (Authorization Code, Client Credentials, or both). Note the Consumer Key and Consumer Secret, and add the redirect URI.
- For SuiteApp distribution: register the SuiteApp via SuiteApp Marketplace and pass Oracle SuiteApp review (single-customer installs skip this).
- The authenticating user must have a role with
REST Web Services+ appropriate inventory permissions (Items, Locations, Inventory Adjustments — Full or View as needed).
Configure in admin
Section titled “Configure in admin”- Open
/platformsin the admin UI, filter to Inventory, click NetSuite Inventory. - Fill Configure:
clientId— Consumer Key from the Integration Record.clientSecret— Consumer Secret from the Integration Record.accountId— the customer’s NetSuite account id (with_SB1suffix for sandboxes).redirectUri—${PUBLIC_BASE_URL}/auth/inventory/netsuite-inventory/callback.
- Enable the adapter.
Required scopes
Section titled “Required scopes”NetSuite uses a single rest_webservices scope (plus restlets and suite_analytics for the other surfaces). The effective permissions come from the NetSuite role the connecting user holds. Lock that role down to the inventory + items + locations + warehouse permissions.
Webhooks
Section titled “Webhooks”NetSuite does not provide first-class outbound webhooks. The canonical near-real-time mechanism is a User Event Script (SuiteScript 2.x) deployed to inventory record types that pushes to an external URL on afterSubmit. Sign these outbound calls with a shared secret HMAC-SHA256 in an X-Netsuite-Signature header (hex) — the adapter verifies against the configured secret.
For pure pull integrations, use SuiteQL + the lastModifiedDate filter on items / inventoryitemlocations / inventoryadjustment for delta sync.
Quirks worth knowing
Section titled “Quirks worth knowing”- AccountID is in every URL. Production:
1234567.suitetalk.api.netsuite.com. Sandbox:1234567_SB1.suitetalk.api.netsuite.com. Release preview:1234567_RP.suitetalk.api.netsuite.com. Mixing them issues tokens that don’t authenticate. - TBA is the legacy mechanism. Token-Based Authentication (TBA) is still supported but Oracle is steering integrations to OAuth 2.0 — prefer OAuth 2.0 for new builds.
- Role permissions cap everything. A correct token + wrong role = silent permission errors. Audit the role under Setup → Users/Roles → Manage Roles.
- Inventory location semantics.
inventoryitemlocationscarries on-hand by location; the baseinventoryitemonly summarises across locations. Don’t confuse them in transforms. - SuiteApp review is mandatory for marketplace distribution. Allow 4-8 weeks; static analysis findings are common blockers.
References
Section titled “References”- OAuth 2.0 Authorization Code Grant Flow
- OAuth 2.0 in NetSuite
- REST Web Services with OAuth 2.0 (community walkthrough)
opensteward.dev ·Plans and free license ·Terms ·Privacy ·support@opensteward.dev
© 2026 Falco Consulting AB. Built from open-steward/opensteward@a3961d8. This site sets no cookies, runs no analytics and loads nothing from other sites, except platform logos from Brandfetch on the Platforms page.