agentsclimarketplace

Acumatica

Skill apideck-libraries/api-skills/skills/acumatica

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.

Install
npx -y skills add apideck-libraries/api-skills --skill acumatica

Assembled 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

Acumatica 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 Acumatica. Routes through Apideck with serviceId "acumatica".

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

7.2 KB, as published. Nobody here has run it

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

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:

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

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

For the raw OpenAPI spec:

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 entityApideck Accounting resource
AR Invoiceinvoices
AP Billbills
Paymentpayments
Credit Memocredit-notes
GL Transactionjournal-entries
Accountledger-accounts
Customercustomers
Vendorsuppliers
Inventory Iteminvoice-items
Taxtax-rates
Purchase Orderpurchase-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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.