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
- Partnership Required
- Yes(Sage Intacct Marketplace Partner Program is required. Apideck can facilitate the introduction.)
- Partnership Application
- Sage Intacct Marketplace↗
- Apideck Credentials
- AvailableAvailable for sandbox only — production integrations require your own Marketplace Partner credentials.
- Account Type Required
- Sage Intacct with Web Services subscription enabled
- Sandbox Availability
- Available(Provisioned by Sage Intacct upon contract execution; also available via Apideck temporary shared sandbox (enterprise contract required — contact Apideck Support).)
- Authentication Method
- OAuth 2.0
- Consumer Access Level
- Any Sage Intacct user with Web Services enabled and the Sender ID authorized in their company
What are Apideck credentials?
For select connectors, Apideck has established partnerships allowing you to integrate immediately without your own partnership. When using Apideck credentials, “Apideck” appears as the requesting application during OAuth. Learn more about partnership categories →
Prerequisites & considerations
- Partnership: Sage Intacct Marketplace Partner Program required (Apideck can facilitate the introduction)
- Partnership costs: $2,500/year (due net 30 from contract execution) + $0.015 per API call once consumers are live
- Approval process is multi-step: security questionnaire, discovery meeting, contract execution, development, API review, technical documentation, live demo call
- Connection limits: none imposed by Apideck
- IP whitelisting: not required
- Sender credentials: Sender ID and Sender Password (issued by Sage Intacct upon contract execution)
- API protocol: XML/SOAP (Sage Intacct Web Services)
- Rate limits vary by the consumer's Sage Intacct service level (not publicly documented); the Standard service level allows 2 concurrent jobs per company
- For your consumers: Sage Intacct with the Web Services subscription enabled (contact account manager if not active). They must authorize your Sender ID in company Web Services settings and create or designate a Web Services user. Credentials needed: Company ID, User ID, Password.
Responsibility matrix
| Area | Apideck | Partner | Customer |
|---|---|---|---|
| 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 | Logs & alerts | Can revoke anytime | ✓ Via dashboard |
Environments
- Sandbox
- Sandbox Sender ID (separate from production) is provisioned by Sage Intacct after contract execution. An Apideck temporary shared sandbox is also available for Enterprise contracts (contact Apideck Support); the shared sandbox uses Apideck's own Sender ID.
- Production
- Production uses your own Sender ID plus the consumer's Company ID, User ID, and Password. ⚠️ Sandbox Sender ID credentials are separate from production — do not use sandbox Sender IDs with production consumer accounts.
🚨Important to Know About Sage Intacct
Authentication & Setup
- Custom auth (not OAuth). You hold the Sender ID (partner-level); consumers provide Company ID, User ID, and Password
- Each consumer must explicitly authorize your Sender ID in their company's Web Services settings — connections fail silently if this step is missed
- Sandbox and production Sender IDs are separate — not interchangeable
Platform Limitations
- Multi-entity companies require the entity/location ID in API calls — misconfiguration causes data access failures
- Standard service level: 2 concurrent jobs per company (3rd request held)
- Mandatory custom fields on standard objects can cause write failures if unmapped
Partnership & Costs
- Partnership fees: $2,500/year + $0.015 per API call once consumers are live
- Multi-step approval: security questionnaire, discovery meeting, contract, API review, technical demo
- 4–8+ weeks from request to production approval
Webhooks
- No native webhooks — Apideck provides Virtual Webhooks (polling-based change detection)
- Rate limits vary by consumer SLA — not publicly documented
⚠️
14 gotchas across 8 resources
Connector-specific behaviors and limitations to be aware of
📦
28 supported resources
View field mappings, supported operations, and schema details