Sage Intacct API Limits: What Are They? Why Should You Care?

Sage Intacct has started enforcing their API transaction limits under the rules of their new Performance Tiers. If you are using Smart Events or Triggers that use the Intacct API, use the AJAX API for page scripts, or are subscribed to the Web Service Developer License and have an integration that you’ve created – this affects you.

performance tiers

There are five different performance tiers, and each one comes with a different number of transactions that you can perform monthly without being charged with an overage fee. With your Intacct subscription, you are automatically enrolled in Performance Tier 1. This tier allows for 100,000 transactions per month. If that is not enough transactions for your needs, you can upgrade to a higher tier for an additional fee. Reach out to your CSM to acquire exact pricing.

what's considered a transaction?

Sage Intacct defines a transaction as any API call that involves a query,readByQuery, create,update, or deletecommand.   Even if you batch multiple create objects within a single API call, Intacct considers each createto be one transaction. When creating objects that have line items, like an APBILL, each header object is considered a transaction – the amount of line items on a single bill do not impact transaction counts. Here are some examples:

• If you were to create five AP Bills each with ten line items, the total Intacct transaction count is five.
• If you were to issue a query command on the APBILL object to find how many bills were created this month and receive 100 results, the total Intacct transaction count is one.
• If you were to issue a query command on the APBILL object to find how many bills were created this decade and the result indicates that there are 5,500 APBILL objects that fit this filter parameter – you will need to utilize the offset parameter to receive all 5,500 results since Intacct limits the results to 2,000 results per query command; the total Intacct transaction count is three transactions:
  
  • The first query will have an offset of 0 and return 2,000 results
  • The second query will have an offset of 2000 and return the next 2,000 results
  • The third query will have an offset of 4000 and return the final 1,500 results

finding your current usage

Any user with administrative level access or have a role that has been granted “Usage Insights” access in the Administration module is able to view the current API Transaction counts. To find the report, navigate to Company -> Admin (tab) -> Usage Insights -> API Usage (tab). You are only responsible for the API transactions that were created by these “Applications”:

• ajax: This is the sender ID that is used by custom page scripts that query the AJAX API.
• SMART_EVENT: This is the sender ID that is used by your Smart Events that use the Intacct API
• PLATFORMAPI: This is the sender ID that is used by Triggers that use the Intacct API
• [Your Sender ID]: If you have a web services developer license subscription, this is your sender ID that you created when you activated that subscription.

If you are subscribed to the Web Service Developer License and you are using the API in that method, please be aware that this report currently only includes API transactions that are made with the XML API. To see usage with the REST API, you can view this in your developer workspace. Sage is working on a way to include the REST API in this usage report so that everything is easily accessible in one place.

overages

If you go over the allotted number of transactions in a month, you will receive a bill for the overage.   Intacct charges the overages in “packs” of ten transactions. The method to calculate any overage fees you may receive would be:

([Total amount of transactions that month] – [Performance Tier Allotment]) / 10 * overage fee

The overage fee may vary depending on your performance tier. As of the time of this article, the current rate for Performance Tier 1 subscribers is $0.15 per “pack” of overages. For an example, if a Performance Tier 1 subscriber made 123,456 transactions in a month, the overage would calculate out to be $351.84.

(123,456 – 100,000) / 10 * $0.15 = $351.84

strategies to avoid overage

If you find your transaction counts are over or close to being over your allotted amount for the month, there are a few simple changes you can make to optimize usage.

Click here for more tips on optimizing XML API usage. Contact our development team to help reduce your API transaction counts, and reach out now before you get hit with overage fees!

Want More Sage Intacct Features & Functions?

For more Sage Intacct Tips & Tricks videos, visit our YouTube page and subscribe to stay up-to-date with the latest insights and tutorials. Our channel is dedicated to providing valuable resources for businesses looking to optimize their financial management with Sage Intacct.

Check out these blogs to help get you started!

Uploading Your Budgets Using Pre-Built Templates
How To Create Ad-Hoc Reports Using Views and Filters
Creating Expanded Columns and a Summary for Reports