Sage Intacct
Service ID: sage-intacct
Increase ROI and transform your organization with the first and only preferred provider of the AICPA for accounting and financial management software for companies of any size.
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.
- Webhooks
- Virtual webhooks — created, updated and deleted events across 9 resource families. Sage Intacct has no native webhooks.
- Partnership Required
- Yes(A Sage Web Services developer license is required, via the Marketplace Partner Program. Apideck facilitates the introduction to Sage's Marketplace Partner team.)
- Partnership Application
- Sage Intacct Marketplace↗
- Apideck Credentials
- Not available(Not available — you supply the Sender ID once at integration level, and each consumer supplies their own Sage Intacct company login.)
- Costs
- Sage Intacct Marketplace Partner Program membership is $2,500/year, plus $0.015 per API call once your consumers are live. Effective August 2026.
- Sandbox Availability
- Available(Sage provisions a sandbox with its own Sender ID on contract execution. Apideck's temporary shared sandbox requires an enterprise contract.)
- 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
- Sage Performance Tier 1 (default): 100K API transactions/month. One API plus one offline report job per company; a third waits 30s and errors if no spot opens.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Initiate Sage Intacct Partnership | ✓ | — | Facilitates introduction |
| Complete Security Questionnaire | ✓ | — | — |
| Execute Marketplace Partner Contract | ✓ | — | — |
| Configure Sender ID in Apideck | ✓ | — | Dashboard available |
| Enable Web Services | — | ✓ | Instructions provided |
| Authorize Sender ID | — | ✓ | Instructions provided |
| Create Web Services User | — | ✓ | Instructions provided |
| Provide Credentials | — | ✓ | Secure connection form |
| Build via Unified API | ✓ | — | Maintains connector |
| Complete API Review & Demo | ✓ | — | Support available |
| Monitor Connections | ✓ Via dashboard | Can revoke anytime | Logs & alerts |
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.
🚨Important to Know About Sage Intacct
- Sage titles this surface "About the XML API (Legacy)" and steers new work to REST. No sunset is announced and existing integrations stay supported, but legacy functions get no enhancements and individual legacy objects have been retired — weigh that on a long-term build.
- If a consumer skips authorizing your Sender ID in their company's Web Services settings, every call fails with errorno XL03000006, "Invalid Web Services Authorization", naming the unauthorized Sender ID.
- Approval process is multi-step (security questionnaire, discovery meeting, contract execution, development, API review, technical documentation, live demo call).
- Multi-entity companies require the entity/location ID in API calls — misconfiguration causes data access failures.
⚠️
27 gotchas across 15 resources
Connector-specific behaviors and limitations to be aware of
📦
30 supported resources
View field mappings, supported operations, and schema details