acumatica
Acumatica (via Apideck)
Access Acumatica 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, banqUP, Campfire 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 Acumatica plumbing.
Beta connector. Acumatica is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
acumatica - Unified API: Accounting
- Auth type: oauth2
- Status: beta
- Apideck setup guide: Connection guide
- Gotchas: page
- Acumatica docs: https://help.acumatica.com
- Homepage: https://www.acumatica.com/
When to use this skill
Activate this skill when the user explicitly wants to work with Acumatica — for example, "create an invoice in Acumatica" or "reconcile payments in Acumatica". This skill teaches the agent:
- Which Apideck unified API covers Acumatica (Accounting)
- The correct
serviceIdto pass on every call (acumatica) - Acumatica-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 Acumatica
const { data } = await apideck.accounting.invoices.list({
serviceId: "acumatica",
});
Portable across 34 Accounting connectors
The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Acumatica to another Accounting connector is a one-string change — no rewrite, no new SDK.
// Today — Acumatica
await apideck.accounting.invoices.list({ serviceId: "acumatica" });
// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "banqup" });
This is the compounding advantage of using Apideck over integrating Acumatica 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.
Acumatica via Apideck Accounting
Acumatica is a cloud ERP platform for mid-market businesses, with strong distribution, manufacturing, and services verticals. Apideck coverage targets the core financial management surface.
Entity mapping
| Acumatica entity | Apideck Accounting resource |
|---|---|
| AR Invoice | invoices |
| AP Bill | bills |
| Payment | payments |
| Credit Memo | credit-notes |
| GL Transaction | journal-entries |
| Account | ledger-accounts |
| Customer | customers |
| Vendor | suppliers |
| Inventory Item | invoice-items |
| Tax | tax-rates |
| Purchase Order | purchase-orders |
Coverage highlights
- ✅ Full CRUD on invoices, bills, payments, customers, suppliers
- ✅ Journal entries
- ✅ Purchase orders
- ✅ Credit notes
- ⚠️ Acumatica Generic Inquiries — powerful custom reports; not exposed, use Proxy
- ❌ Manufacturing and distribution modules — use Proxy for BOM, work orders, shipments
- ❌ Payroll
Auth notes
- Type: OAuth 2.0, managed by Apideck Vault
- Tenant + branch binding: Acumatica supports multi-tenant + multi-branch. The connection is bound to one tenant; branch selection is typically passed per call.
- Screen-based APIs: Acumatica has both OData-style REST and "Screen-Based" Contract API. Apideck abstracts this; Proxy calls can hit either.
Example: create an AR invoice
const { data } = await apideck.accounting.invoices.create({
serviceId: "acumatica",
invoice: {
customer_id: "cust_abc",
invoice_date: "2026-04-18",
line_items: [
{ description: "Consulting", quantity: 10, unit_price: 150 },
],
currency: "USD",
},
});
Escape hatch: Proxy API
When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Acumatica directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Acumatica'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: acumatica" \
-H "x-apideck-downstream-url: <target endpoint on Acumatica>" \
-H "x-apideck-downstream-method: GET"
See Acumatica'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), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, exact-online-nl (beta), and 25 more.
See also
- Apideck connection guide for Acumatica
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Acumatica official docs
More from apideck-libraries/api-skills
apideck-connector-coverage
Check Apideck connector API coverage before building integrations. Use when determining which operations a connector supports, comparing connector capabilities, or diagnosing why an API call fails with a specific connector. Teaches agents to query the Connector API for real-time coverage data.
18apideck-best-practices
Best practices for building Apideck integrations. Covers authentication patterns, pagination, error handling, connection management with Vault, webhook setup, and common pitfalls. Use when designing or reviewing any Apideck integration regardless of language.
18apideck-rest
Apideck Unified REST API reference for any language. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using direct HTTP calls. Covers authentication headers, CRUD operations, cursor-based pagination, filtering, sorting, error handling, rate limiting, pass-through parameters, and webhooks. Language-agnostic — works with curl, fetch, axios, httpx, or any HTTP client.
16apideck-portman
API contract testing with Portman by Apideck. Use when generating Postman collections from OpenAPI specs, writing contract tests, variation tests, integration tests, fuzz testing, or setting up CI/CD API test pipelines. Portman converts OpenAPI 3.x specs into Postman collections with auto-generated test suites.
14apideck-node
Apideck Unified API integration patterns for TypeScript and Node.js. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors. Covers the @apideck/unify SDK, authentication, CRUD operations, pagination, filtering, webhooks, and Vault connection management.
14apideck-codegen
Generate typed API clients from Apideck OpenAPI specs using code generators. Use when the user wants to generate custom SDK clients, typed models, API stubs, or server scaffolding from Apideck's published OpenAPI specifications. Covers openapi-generator, Speakeasy, and Postman import workflows.
14