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 + Multi-Step Approval
- Partnership Required
- Yes(Sage Intacct Marketplace Partner Program — Apideck intro available)
- Partnership Application
- Developer Portal↗
- Apideck Credentials
- Available
- Account Type Required
- Sage Intacct with Web Services subscription enabled
- Sandbox Availability
- Available(Provisioned by Sage Intacct after contract; Apideck shared sandbox available for Enterprise contracts)
- Authentication Method
- OAuth 2.0
- Consumer Access Level
- Any Sage Intacct user with Web Services enabled and the Sender ID authorized in their company
🚨Important to Know About Sage Intacct
Partnership & Approval
- Marketplace Partner Program contract required before development begins
- Partnership fees: $2,500/year + $0.015 per API call once live
- Multi-step process: security questionnaire, discovery meeting, contract, API review, technical demo
- 4–8+ weeks from request to production approval
Authentication
- Custom auth (XML/SOAP) — not OAuth
- Two-level credentials: partner Sender ID + consumer Company/User/Password
- Consumers must explicitly authorize the Sender ID in Web Services settings
- Sender credentials never expire unless manually changed; user passwords follow company policy
- Sandbox and production Sender IDs are separate — not interchangeable
Platform Limitations
- XML/SOAP API only — REST is in early availability
- Web Services subscription must be enabled per consumer (not on all plans by default)
- Multi-entity companies require correct entity/location ID in calls
- Standard service level: 2 concurrent jobs per company; 3rd request held 30s
- Mandatory custom fields on standard objects can cause write failures if unmapped
Webhooks & Sorting
- No native webhooks — Apideck provides Virtual Webhooks
- Limited sort support via XML API; sort client-side where needed
- Rate limits vary by consumer SLA — not publicly documented
⚠️
11 gotchas across 6 resources
Connector-specific behaviors and limitations to be aware of
📦
28 supported resources
View field mappings, supported operations, and schema details