NetSuite
live · conformance passing
Models the NetSuite REST Web Services an ERP integration actually uses — customers, the chart of accounts, non-inventory and service items, invoices with sublists and server-computed totals, customer payments and the receivables they settle, SuiteQL and the metadata catalog — with OAuth 1.0a token-based authentication, realm-scoped accounts, offset paging, idempotency keys and Oracle's problem-detail envelope.
- Category
- ERP
- Sandbox key
- issued by the sandbox
- Verified against
- netsuite 0.12.0
- Replaces
- A NetSuite sandbox account whose numbering nobody can reset
Scenarios
Start a sandbox in one of these, or describe the state you want in a sentence and the seeder writes the records it implies.
Overdue receivables
A customer with three invoices past their due date, one of them part paid, for collections and ageing logic.
Concurrency exhausted
The account starts with no concurrent web service slots left, so the next request is answered 429.
Restricted role
The credential is live but the role cannot touch invoices, so every request to one is answered 403.
What it models
Records your code can read, write and edit for the life of the sandbox. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- customer
- account
- item
- invoice
- customerpayment
- subsidiary
- currency
- companyinfo
- idempotency
Verified in CI against
- pythonnetsuite0.12.0