NetSuite integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in NetSuite. Routes through Apideck with serviceId "netsuite".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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.
netsuiteActivate 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:
serviceId to pass on every call (netsuite)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-restFor the raw OpenAPI spec:
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",
});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 is Oracle's enterprise ERP. Apideck abstracts the SuiteTalk REST API; deep coverage for finance operations but less for NetSuite's broader ERP surface.
| NetSuite record | Apideck Accounting resource |
|---|---|
| Invoice | invoices |
| Vendor Bill | bills |
| Customer Payment / Vendor Payment | payments |
| Journal Entry | journal-entries |
| Account | ledger-accounts |
| Customer | customers |
| Vendor | suppliers |
| Item | items |
| Purchase Order | purchase-orders |
| Subsidiary | subsidiaries |
custom_fields[]; custom records need ProxyTSTDRV) — the user picks the right one during OAuth.const { data } = await apideck.accounting.invoices.list({
serviceId: "netsuite",
filter: { status: "open", subsidiary_id: "1" },
});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.
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.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patterns9e04d86
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.