Sage Intacct

At a Glance

Difficulty

⚠️INVOLVEDPartnership + Custom Auth + Multiple Approvals

Authentication

OAuth 2.0Custom 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).

Partnership Required

Yes(Sage Intacct Marketplace Partner Program is required. Apideck can facilitate the introduction.)

Partnership Application

Sage Intacct Marketplace↗

Apideck Credentials

Not available(Not available — consumers supply their own Sage Intacct credentials (Sender ID plus company/user login).)

Costs

Partnership costs: $2,500/year (due net 30 from contract execution) + $0.015 per API call once consumers are live.

Sandbox Availability

Available(Provisioned by Sage Intacct upon contract execution; also available via Apideck temporary shared sandbox (enterprise contract required — contact Apideck Support).)

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

Rate Limits

Vary by the consumer's Sage Intacct service level (not publicly documented); the Standard service level allows 2 concurrent jobs per company.

Responsibility matrix

Environments

Sandbox

The sandbox Sender ID is provisioned by Sage Intacct after contract execution. The Apideck temporary shared sandbox uses Apideck’s own Sender ID.

Production

⚠️ Sandbox Sender ID credentials are separate from production — do not use sandbox Sender IDs with production consumer accounts.