API transaction volume, concurrency, and scaling

The Sage Intacct REST API is built on a modern cloud platform that supports elastic scaling to accommodate integrations of varying volumes. To provide predictable throughput, Sage Intacct offers performance tiers, each defining entitlements for API transaction volume, concurrent API requests, and concurrent offline processes.

These entitlements allow you to design and scale your integration with a clear understanding of system limits and expected capacity.

API transaction entitlement

The API transaction entitlements are designed to operationally support anticipated API transaction volume by assigning server resources to companies, according to their needs.

API transaction entitlements apply only to a company’s own integrations and usage. API transactions from authorized Marketplace Partners, ISV solutions, and Sage Intacct’s own applications do not count against the Performance Tier transaction entitlement purchased by a customer.

Companies that exceed their monthly Performance Tier API transaction entitlement are charged an overage fee for the API transactions which exceed their tier entitlement. Sage Intacct does not block API transactions that exceed the API transaction entitlement. To gain insights about the transaction volume for your company, you can access REST API metrics from your workspace. To learn more, see REST developer API metrics.

API concurrency entitlement

Sage Intacct implements concurrency limits on REST API calls. These limits prevent any one Sage Intacct customer from consuming server resources at the expense of other customers.

Note that concurrency does not equate to the number of integrations. A single integration can exceed the concurrency limits if developed to support multiple, parallel processes. Similarly, multiple integrations may safely operate within concurrency limits if the integrations issue small requests that do not overlap for more than two seconds.

To prevent a single integration from consuming all available concurrent processes, Sage Intacct provides higher concurrency for a company than for any single integration. This is expressed in the form of application/company in our API concurrency tiers. For example, 6/8 indicates that any single application can use up to 6 API processes at a single point in time, while the company can use up to 8 concurrent API processes in total.

Offline processes

Sage Intacct limits the number of offline processes per company. Companies use these offline processes for activities such as scheduled transactions and offline reports. At our standard Performance Tier 1, Sage Intacct limits each company to one (1) concurrent offline process. Queues for offline processes are shared with other companies. So, it is possible that even if a company only has one job in the queue, they will wait in line behind other companies. Premium performance tiers offer more concurrency to offline processes and offer isolation from other companies, eliminating waits behind other companies.

Performance tiers

Each performance tier specifies a limit for transaction volume, concurrent API requests per application/company, and offline process concurrency. The following table lists the standard entitlements for each tier:

To learn more about performance tiers and which tier best suits your needs, please contact your Sage Intacct account manager.