Netsuite
Skill apideck-libraries/api-skills/providers/claude/plugin/skills/netsuite
One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.
npx -y skills add apideck-libraries/api-skills --skill netsuiteAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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".
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.9 KB, ~1.7k tokens by cl100k_base, as published. Nobody here has run it
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
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:
- Which Apideck unified API covers NetSuite (Accounting)
- The correct
serviceIdto pass on every call (netsuite) - 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, orapideck-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
| 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 |
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 checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- NetSuite official docs