Sage Intacct

Sage Intacct (via Apideck)

Access Sage Intacct 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 Sage Intacct plumbing.

Quick facts

• Apideck serviceId: sage-intacct
• Unified API: Accounting
• Auth type: oauth2
• Apideck setup guide: Connection guide
• Gotchas: page
• Sage Intacct docs: https://developer.intacct.com
• Homepage: https://www.sageintacct.com/

At a glance

• Implementation difficulty: involved — Partnership + Custom Auth + Multiple Approvals
• Vendor partnership required: yes (Sage Intacct Marketplace) — Sage Intacct Marketplace Partner Program is required. Apideck can facilitate the introduction.
• Apideck-managed credentials: Not available — consumers supply their own Sage Intacct credentials (Sender ID plus company/user login).
• Account type required: Sage Intacct with Web Services subscription enabled
• Consumer access level: Any Sage Intacct user with Web Services enabled and the Sender ID authorized in their company
• Sandbox: available — Provisioned by Sage Intacct upon contract execution; also available via Apideck temporary shared sandbox (enterprise contract required — contact Apideck Support).
• Costs: Partnership costs: $2,500/year (due net 30 from contract execution) + $0.015 per API call once consumers are live.
• Rate limits: Vary by the consumer's Sage Intacct service level (not publicly documented); the Standard service level allows 2 concurrent jobs per company.
• Authentication: Custom authentication — Sage Intacct XML Web Services using a Sender ID. Despite an OAuth2 label in the connector config, this is not a standard OAuth grant: consumers provide Company ID / User ID / password credentials manually, exchanged for a session token.
• Webhooks: No native webhooks — Apideck provides Virtual Webhooks (polling-based change detection).

Important to know:

• Each consumer must explicitly authorize your Sender ID in their company's Web Services settings — connections fail silently if this step is missed.
• Approval process is multi-step (security questionnaire, discovery meeting, contract execution, development, API review, technical documentation, live demo call) and takes 4–8+ weeks from request to production approval.
• Multi-entity companies require the entity/location ID in API calls — misconfiguration causes data access failures.

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

When to use this skill

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

1. Which Apideck unified API covers Sage Intacct (Accounting)
2. The correct serviceId to pass on every call (sage-intacct)
3. Sage Intacct-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 Sage Intacct
const { data } = await apideck.accounting.invoices.list({
  serviceId: "sage-intacct",
});

Portable across 34 Accounting connectors

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

// Today — Sage Intacct
await apideck.accounting.invoices.list({ serviceId: "sage-intacct" });

// 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 Sage Intacct 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.

Sage Intacct via Apideck Accounting

Sage Intacct is a cloud accounting platform for mid-market. Apideck covers core finance entities.

Entity mapping

Coverage highlights

• ✅ CRUD on invoices, bills, payments, customers, suppliers, items
• ✅ Multi-entity support (Intacct's Company structure)
• ✅ Multi-currency
• ⚠️ Dimensions (Department, Location, Class, Project) — exposed as custom fields where available
• ❌ Sage Intacct REST (beta) — separate auth-only connector; use standard XML connector via Apideck

Auth

• Type: Basic auth (username / password + company ID), managed by Apideck Vault
• Company ID required: the user provides their Intacct Company ID alongside credentials — it's a per-tenant identifier, not a global login.
• Sender credentials: Apideck's Vault app already has the required Sender ID/password registered with Sage; the end-user provides only their own Intacct login.
• Web Services subscription required: Sage Intacct customers need the Web Services add-on enabled on their Intacct subscription before any API access works. If auth fails with "API not enabled," direct the user to their Intacct admin.

Example: list invoices posted in last month

const { data } = await apideck.accounting.invoices.list({
  serviceId: "sage-intacct",
  filter: { updated_since: "2026-03-01T00:00:00Z" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Sage Intacct directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Sage Intacct'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: sage-intacct" \
  -H "x-apideck-downstream-url: <target endpoint on Sage Intacct>" \
  -H "x-apideck-downstream-method: GET"

See Sage Intacct'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 Sage Intacct
• 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
• Sage Intacct official docs