Developer ToolsFree calculatorPDF, Excel, Word exportAcumaticaSMB Manufacturing

Acumatica API Request Capacity Calculator

Integrations that look light on paper can saturate an ERP when every record is its own call. This calculator converts records, sync frequency and batch size into calls per minute and the number of API sessions you need, so you can design before the limits bite.

Your numbers

count

Ecommerce, EDI, shipping, CRM, BI extracts.

records
runs
25 records

Where the endpoint accepts batches or you page results; 1 means one call per record.

seconds
60 %
per minute

Read it from your Acumatica licence and service level; the limit depends on the licence.

Your results

Average calls per minute
4.2667
API sessions needed
1
API calls per hour
256
Session busy time
5.7%
Share of an hour that one session would be busy making these calls.
Headroom against licensed limit
96.4%
Negative means the average load already exceeds the limit.

Average load only. Bursts at the top of the hour can be much higher than the average; check your licence for the exact limits that apply.

Save results:

Calls per minute by batch size

Sweeps Records per API call from 1 to 200, holding your other inputs fixed.

Integration design review

Send your integration list and schedule and we will look for batching and scheduling improvements.

Optional. The tool and every export work without this. No spam.

How to use it

List each integration's average records per sync and runs per hour, using the sum if integrations differ. Set records per call to the real batch or page size your code uses. Enter the average call duration measured from logs. Then read the calls per minute, sessions needed and the headroom against the request limit in your licence.

The arithmetic

Calls per hour is integrations x runs x ceil(records / batch). Busy time is calls x duration divided by 3,600 seconds. Sessions are busy time divided by a target utilisation, rounded up, since a session cannot run flat out without queueing. Headroom is the unused share of the licensed per-minute limit. Larger batches reduce calls sharply at first and flatten later, as the chart shows.

  • Log out API sessions explicitly; idle sessions hold licence slots.
  • Spread schedules instead of firing every integration on the hour.
  • Use paging and filters to cut payload, not just call count.

Common mistakes

The average hides peaks: ten jobs scheduled at minute zero look like a tenth of the traffic in the average but arrive all together. Test with a burst scenario, add retry traffic from failures, and include reporting and BI pulls that run during business hours. If you are close to the limit, redesign before buying capacity.

Frequently Asked Questions

What are Acumatica's API limits?

Limits depend on your licence and service level, such as requests per minute and concurrent API users. Check your licence terms rather than relying on a generic number.

Why does batch size matter?

Each call has fixed overhead for authentication, network and processing. Fewer larger calls reduce that overhead, until payload size or timeouts become the limiting factor.

Does this cover OData or generic inquiries?

The model is generic: any request that counts against your limit. Replace records per call with the page size you use for an OData or inquiry pull.

What utilisation should I target?

Around 60 percent leaves room for bursts and retries. Higher targets increase queueing delay and timeouts when many jobs start together.

Netray can review your integration design and logs and suggest batching, scheduling and caching changes.