The API Report CardAPI Index
Sage Intacct

Sage Intacct API

Accounting ERP software · sage.com

Sage Intacct runs two parallel APIs: a modern REST surface with OAuth 2.0 and an older XML API that still covers more objects. Each customer must authorize your Sender ID manually, and the base plan caps API usage at 100,000 transactions a month with paid overage.

Last verified: July 2026Accounting & Tax
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo documented public APIs: a REST API with an OpenAPI spec at developer.sage.com and the long standing XML API.
AccessPOOREach customer must authorize your Sender ID in security settings; the base plan caps 100,000 transactions a month with paid overage.
CoveragePOORFeature coverage is split across REST and legacy XML; reaching the full object surface means maintaining both stacks.
AuthPOORPer-customer Sender ID authorization is manual, and OAuth access tokens are short lived with rotating refresh tokens.
Docs & DXGOODTwo public developer portals, an OpenAPI spec, sandbox environments, and webhooks via Smart Events and REST triggers.
StabilityMIXEDThe XML API is legacy yet still broader than REST, so long-lived integrations straddle a migration in progress.
MORE FROM THE REPORT CARD
Supergood: Sage Intacct has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Sage Intacct scores D+ on the API Report Card. Sage Intacct runs two parallel APIs: a modern REST surface with OAuth 2.0 and an older XML API that still covers more objects. Each customer must authorize your Sender ID manually, and the base plan caps API usage at 100,000 transactions a month with paid overage.

Tried to integrate with Sage Intacct?
SOURCES
Performance Tier model, default Tier 1 caps usage at 100,000 transactions/month with overage billed at ~$0.15 per 10-transaction pack; every query, readByQuery, create, update, delete counts as one transaction getknit.dev
GW-0010 / HTTP 429 throttling fires aggressively under bulk loads; consumers must implement exponential backoff and request queuing dmconsultant.co
Two parallel APIs (XML legacy + REST) with split feature coverage forces integrators to maintain both stacks for full object surface developer.sage.com
Per-customer Sender ID + Web Services User + explicit security-settings authorization makes per-customer onboarding manual and admin-gated getknit.dev
OAuth 2.0 access tokens are short-lived and refresh tokens rotate, requiring durable token-management infrastructure developer.sage.com
Query results capped at 2,000 records per call, large pulls require pagination loops that burn into the transaction cap getknit.dev
Smart Events / webhooks are limited compared to modern SaaS APIs; many integrators end up polling for changes developer.sage.com
Initial historical sync is restricted, only data created or modified in the last ~6 months is exposed in some flows, complicating full backfills apiworx.com
Sage Intacct Web Services does not accept JSON, XML-only on the legacy surface, despite REST being the recommended path getknit.dev
One concurrent offline process per company on Tier 1, heavy ETL/reporting jobs serialize and can starve other integrations coefficient.io
Customer support is widely described as slow and uneven, tickets can take weeks or months to resolve, with users calling it "probably the worst feature of Intacct" g2.com
Steep learning curve and non-intuitive UI, many tasks require navigating multiple menus or multi-step workflows softwareadvice.com
Difficult to correct posted transactions, reversing or editing entries is cumbersome compared to peers capterra.com
UI performance lag and ~3-second API round trips reported by power users apiworx.com
Per-user licensing plus add-on modules drive TCO up quickly, mid-market deployments commonly land at $50K–$200K/year all-in erpresearch.com
Implementation typically costs 1.0–1.5x the first-year subscription and effectively requires a Sage VAR rklesolutions.com
Functional gaps, purchase requisitioning, expense management, and AP automation often require third-party add-ons innormax.com
Reporting customization is powerful but unforgiving, non-finance users struggle without consultant help gartner.com