NetSuite
Service ID: netsuite
NetSuite is the leading integrated cloud business software suite, including business accounting, ERP, CRM and ecommerce software.
At a Glance
- Difficulty
- π§ADVANCEDCustom Auth + Manual Per-Consumer Token Setup
- Authentication
- CustomToken-Based Authentication (TBA), NetSuite's OAuth 1.0-based scheme β consumers create an integration record and credentials manually; no OAuth redirect.
- Webhooks
- Virtual webhooksβ β created/updated/deleted across 14 accounting resources (invoices, credit notes, quotes, bills, expenses, payments, customers, suppliers, projects and more).
- Partnership Required
- No(Partner Trial accounts are available for extended testing.)
- Partnership Application
- NetSuite Partner Programβ
- Apideck Credentials
- AvailableShared Consumer Key/Secret ship with Apideck's NetSuite SuiteBundle (ID 705521); consumers still supply their own Account ID and Token ID/Secret.
- Costs
- No additional platform fees, and no connection limits imposed.
- Sandbox Availability
- Available β Access Sandboxβ(Via Apideck's temporary shared sandbox (enterprise contract required β contact Apideck Support).)
- Account Type Required
- NetSuite with SuiteTalk (Web Services) and Token-Based Authentication enabled
- Consumer Access Level
- Administrator, or a custom role with access-token login, both SOAP and REST Web Services, and accounting list/setup permissions
- Rate Limits
- Per-account concurrency (not requests/minute): 5 Standard, 15 Premium, 20 Enterprise/Ultimate, +10 per SuiteCloud Plus license; Apideck retries automatically.
What are Apideck credentials?
For select connectors, Apideck has established partnerships allowing you to integrate immediately without your own partnership. When using Apideck credentials, βApideckβ appears as the requesting application during OAuth. Learn more about partnership categories β
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Request Sandbox Access | β | β | Provides (enterprise contract) |
| Enable TBA & SuiteTalk | β | β | Instructions provided |
| Create Integration Record | β | β | Instructions provided |
| Configure Role & Permissions | β | β | Instructions provided |
| Generate Access Token | β | β | Instructions provided |
| Provide Credentials | β | β | Secure connection form |
| Build via Unified API | β | β | Maintains connector |
| Monitor Connections | β Via dashboard | Can regenerate tokens | Logs & alerts |
Environments
- General
- NetSuite uses one credential structure everywhere β the Account ID alone determines which instance is reached, and sandbox Account IDs carry a suffix such as _SB1.
- Sandbox
- Purpose: development and testing. Routes: Apideck's temporary shared sandbox or an Apideck-assisted NetSuite sandbox, both requested through Apideck Support (the shared sandbox requires an enterprise contract, and NetSuite charges its own fee for sandbox accounts); the consumer's own sandbox; or a time-limited NetSuite Partner Trial. Oracle does not offer direct trial accounts. β οΈ Tokens do not survive a sandbox refresh β the integration record and access token must be recreated afterwards, which is expected NetSuite behavior.
- Production
- Purpose: live customer data. Credentials: the consumer's own Account ID plus Token ID and Token Secret (and Consumer Key/Secret on the manual route).
π¨Important to Know About NetSuite
- Oracle has scheduled SOAP removal: 2025.2 is the last SOAP endpoint, release 2027.1 blocks new SOAP integrations, and 2028.2 removes SOAP entirely. Apideck already offers NetSuite REST support via Proxy.
- Missing role permissions can fail silently: a filtered list call the role is not permitted for returns 200 OK with an empty result set instead of an error, so an under-permissioned connection looks healthy while returning no data.
- Custom forms can break writes: a mandatory custom field on a standard NetSuite form makes API writes to that record type fail, blocking creates you had tested successfully.
- SuiteTax accounts are supported, but the connection must declare SuiteTax via an optional connection setting β without it, tax data is served from the wrong records.
- A single connection covers a whole OneWorld account: a Default Subsidiary setting scopes most list and report reads to one subsidiary, and a per-request override reaches any other. A parent subsidiary excludes its children; company-info always returns the root.
β οΈ
78 gotchas across 31 resources
Connector-specific behaviors and limitations to be aware of
π¦
33 supported resources
View field mappings, supported operations, and schema details