Netsuite

NetSuite (via Apideck)

Access NetSuite through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant NetSuite plumbing.

Quick facts

• Apideck serviceId: netsuite
• Unified API: Accounting
• Auth type: custom
• Apideck setup guide: Connection guide
• Gotchas: page
• NetSuite docs: https://docs.oracle.com/en/cloud/saas/netsuite/
• Homepage: https://netsuite.com

At a glance

• Implementation difficulty: highly complex — Custom Auth + Manual Per-Consumer Token Setup
• Vendor partnership required: no (NetSuite Partner Program) — Optional — Partner Trial accounts are available for extended testing.
• Apideck-managed credentials: available — Shared Consumer Key/Secret ship with Apideck's NetSuite SuiteBundle (ID 705521); consumers still supply their own Account ID and Token ID/Secret.
• 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
• Sandbox: available (signup) — Via Apideck's temporary shared sandbox (enterprise contract required — contact Apideck Support).
• Costs: No additional platform fees, and no connection limits imposed.
• Rate limits: Per-account concurrency (not requests/minute): 5 Standard, 15 Premium, 20 Enterprise/Ultimate, +10 per SuiteCloud Plus license; Apideck retries automatically.
• Authentication: Token-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 11 accounting resources (invoices, bills, payments, customers, suppliers, projects and more).

Important to know:

• 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.
• OneWorld (multi-subsidiary) accounts need one connection per subsidiary — there is no per-request company-context switching, and company-info resolves to the root subsidiary.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/netsuite (overview field) is the live, authoritative version.

When to use this skill

Activate this skill when the user explicitly wants to work with NetSuite — for example, "create an invoice in NetSuite" or "reconcile payments in NetSuite". This skill teaches the agent:

1. Which Apideck unified API covers NetSuite (Accounting)
2. The correct serviceId to pass on every call (netsuite)
3. NetSuite-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• Accounting: https://specs.apideck.com/accounting.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List invoices in NetSuite
const { data } = await apideck.accounting.invoices.list({
  serviceId: "netsuite",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from NetSuite to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — NetSuite
await apideck.accounting.invoices.list({ serviceId: "netsuite" });

// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });

This is the compounding advantage of using Apideck over integrating NetSuite directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

NetSuite via Apideck Accounting

NetSuite is Oracle's enterprise ERP. Apideck abstracts the SuiteTalk REST API; deep coverage for finance operations but less for NetSuite's broader ERP surface.

Entity mapping

Coverage highlights

• ✅ CRUD on invoices, bills, payments, customers, suppliers
• ✅ Journal entries (posting + drafts)
• ✅ Multi-subsidiary and multi-currency (OneWorld editions)
• ✅ Purchase orders
• ⚠️ Custom records and custom fields — exposed via custom_fields[]; custom records need Proxy
• ❌ SuiteScript, SuiteFlow — out of scope; use Proxy for advanced operations

Auth

• Type: OAuth 2.0, managed by Apideck Vault
• Account binding: each connection is bound to one NetSuite account ID. Sandbox accounts have a distinct suffix (e.g. TSTDRV) — the user picks the right one during OAuth.
• Role selection: NetSuite auth ties to a specific user + role. The role's permissions determine which records are readable/writable. Admin roles are required for broadest coverage — limited roles will 403 on restricted operations.

Example: list open invoices with multi-subsidiary filter

const { data } = await apideck.accounting.invoices.list({
  serviceId: "netsuite",
  filter: { status: "open", subsidiary_id: "1" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call NetSuite directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on NetSuite's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: netsuite" \
  -H "x-apideck-downstream-url: <target endpoint on NetSuite>" \
  -H "x-apideck-downstream-method: GET"

See NetSuite's API docs for available endpoints.

Sibling connectors

Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):

access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.

See also

• Apideck connection guide for NetSuite
• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• NetSuite official docs