Sage Intacct REST

Service ID: sage-intacct-rest

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
⚠️INVOLVEDPaid Web Services Developer License + Per-Consumer Admin Authorization Required
Authentication
OAuth 2.0OAuth 2.0 authorization code grant — a real OAuth flow, unlike the sage-intacct (XML) connector, which uses a Sender ID plus company/user credentials.
Webhooks
Virtual webhooks — created, updated and deleted events across 13 of the supported accounting resources. Sage Intacct has no native webhooks.
Partnership Required
Yes(A Sage Web Services developer license is required — via the Sage Intacct Marketplace Partner Program, or directly from Sage through your account manager.)
Partnership Application
Sage Intacct Marketplace
Apideck Credentials
AvailableAvailable for testing and evaluation — consumers authorize against Apideck's registered Sage application, so the consent screen shows Apideck branding.
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(Registering a Non-production OAuth app is free; a Sage Intacct sandbox company itself is a paid, licensed feature, gated by eligibility and not self-serve.)
Account Type Required
Sage Intacct company with a Web Services subscription
Consumer Access Level
The connection inherits the authorizing Sage Intacct user's role permissions, and a company Admin must authorize the application in each consumer's company.
Rate Limits
Sage Performance Tier 1: 100,000 API transactions/month per company, shared with the XML API. Over-limit: 429 (GW-0010). Headroom: x-downstream-ratelimit-*.

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 →

Responsibility matrix

TaskYou (Customer)Your ConsumerApideck
Obtain Sage Web Services Developer LicenseFacilitates introduction
Execute Marketplace Partner Contract✓ (if taking the Marketplace route)
Register OAuth Application at developer.sage.com/consoleInstructions provided
Authorize ConnectionSecure connection form
Grant Sage Intacct Role PermissionsInstructions provided
Enable Optional Sage Intacct FeaturesInstructions provided
Build via Unified APIMaintains connector
Monitor Connections✓ Via dashboardCan revoke anytimeLogs & alerts

Environments

Sandbox
Testing runs against an application registered at developer.sage.com/console with the Non-production client scope, pointed at a sandbox, trial or developer company. The scope cannot be changed after the application is created, so each environment needs its own registration, and its client credentials are separate from the production ones. A full sandbox company (a copy of production) is requested through a Sage support case and refreshed at most 4 times a year; it is not offered to companies managed through a Sage Intacct multi-entity console or purchased through a reseller. Several modules are unavailable inside a sandbox, including Fixed Assets, Collections, Prepaid Expense Amortization, Advanced Audit Trail and the interactive reporting tools, and a sandbox is valid only to the end of the production billing cycle.
Production
Live companies require an application registered at developer.sage.com/console with the Production client scope, issued once your Web Services developer license is in place. ⚠️ Development credentials CANNOT be used with production accounts.

🚨Important to Know About Sage Intacct REST

  • API tokens are session-bound: signing in to the Sage Intacct web UI as the authorizing user invalidates the token (error REST-2102). Authorize with a dedicated integration user that nobody signs in as interactively.
  • Financial reports stay exclusive to the sage-intacct (XML) connector: REST's reporting endpoints only generate downloadable files asynchronously, never queryable data — a permanent platform gap. Other uncovered Sage endpoints remain reachable via the Apideck Proxy API.
  • The two Sage Intacct connectors are not interchangeable and nothing migrates automatically: switching means authorizing a brand-new connection, and record identifiers do not carry over. Choose one before you build.
  • Two module permissions are easy to miss: quotes need Order Entry — without it, listing returns 403 and creating fails with an error that reads like a company misconfiguration — and customer refunds stay hidden until the feature is enabled in Accounts Receivable.
  • The REST API reached General Availability with Sage's 2025 Release 1 and is the platform Sage recommends for new integrations. The legacy XML/SOAP gateway is frozen and receives no new API objects, so customer refunds and quote creation live only here.
⚠️

45 gotchas across 20 resources

Connector-specific behaviors and limitations to be aware of

📦

27 supported resources

View field mappings, supported operations, and schema details