# NetSuite API Concurrency Limit Calculator > Source: https://netray.co/tools/netsuite-api-concurrency-limit-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Turn request rate and response time into concurrent requests, compare against your account limit, and find the maximum safe call rate. ## Category netsuite ## Erp NetSuite ## Audience - NetSuite developer - Integration architect - NetSuite administrator ## Tool **Kind:** calculator **Inputs:** #### Average calls per minute **Key:** calls_per_min **Type:** number **Default:** 120 **Min:** 1 **Step:** 10 **Unit:** calls/min **Help:** Average request rate from all integrations hitting the same account. #### Average response time **Key:** resp_sec **Type:** number **Default:** 0.8 **Min:** 0.05 **Step:** 0.05 **Unit:** seconds **Help:** Server time per call, including NetSuite script execution. #### Peak to average multiplier **Key:** burst **Type:** select **Default:** 2 **Options:** ##### 1x (steady) **Value:** 1 ##### 2x (typical) **Value:** 2 ##### 3x (bursty) **Value:** 3 ##### 5x (batch dumps) **Value:** 5 #### Account concurrency limit **Key:** limit **Type:** number **Default:** 5 **Min:** 1 **Step:** 1 **Unit:** requests **Help:** Check your own account limit under integration governance. It depends on service tier and SuiteCloud Plus licences. **Outputs:** #### Average concurrent requests **Key:** avg_conc **Expr:** calls_per_min / 60 * resp_sec **Format:** decimal **Description:** Little's law: arrival rate times time in system. #### Peak concurrent requests **Key:** peak_conc **Expr:** avg_conc * burst **Format:** decimal **Primary:** true #### Peak utilization of limit **Key:** util **Expr:** peak_conc / limit * 100 **Format:** percent **Primary:** true #### Headroom at peak **Key:** headroom **Expr:** limit - peak_conc **Format:** decimal **Description:** Negative means requests will queue or be rejected. #### Maximum sustainable average rate **Key:** max_rate **Expr:** limit / (resp_sec * burst) * 60 **Format:** integer **Description:** Calls per minute you can average before the peak reaches the limit. **Chart:** #### Peak concurrent requests vs average calls per minute **Type:** line **X:** calls_per_min **From:** 10 **To:** 600 **Steps:** 30 **Series:** - peak_conc **Disclaimer:** A planning estimate using Little's law. Real concurrency depends on how NetSuite counts requests across SOAP, REST and RESTlet for your account. Confirm your actual limit in the account's integration governance page. ## Content **Intro:** When an integration starts receiving concurrency errors from NetSuite, the usual cause is simple arithmetic: too many calls, each taking too long, arriving at the same time. This calculator makes that arithmetic visible before you go live. **Sections:** #### How to use the calculator **Body:** Enter the average number of calls per minute across every integration that shares the account, then the average response time of those calls. Pick a peak multiplier that matches how your traffic arrives: a polling job is close to steady, while a nightly batch that fires hundreds of calls at once is bursty. Finally enter the concurrency limit that applies to your account. The result shows average and peak concurrent requests, how much of the limit you use at peak, and the highest average call rate you can sustain. #### The formula behind it **Body:** Concurrency equals arrival rate multiplied by the time each request spends in the system. If 120 calls arrive each minute (2 per second) and each takes 0.8 seconds, the average is 1.6 requests in flight. With a 2x peak the system needs 3.2 slots. This is Little's law and it holds for any stable queue. Reducing response time helps as much as reducing call volume, which is why optimising a slow RESTlet often removes concurrency errors without touching the integration. **Bullets:** - Average concurrency = calls per minute / 60 x response seconds - Peak concurrency = average x peak multiplier - Utilization = peak / account limit - Max average rate = limit / (response seconds x multiplier) x 60 #### How to read the result **Body:** Below roughly 70 percent peak utilization you have comfortable margin. Between 70 and 100 percent, a slow response or a retry storm can push you over. Above 100 percent you will see queuing and rejected requests, so reduce the call rate, flatten the peaks, speed up the scripts, or look at what additional concurrency your licence can buy. Remember that the limit is shared: a marketing sync, a warehouse integration and an ad hoc report can all draw from the same pool. #### Common mistakes **Body:** Teams commonly test with one integration and forget the others sharing the account. They also use the median response time instead of a high percentile, which understates concurrency during slow periods. Retries without backoff multiply the problem, because every rejected call adds another. Finally, avoid sizing for the average only. Concurrency errors happen at the peak, not the mean. **Bullets:** - Include every integration and user-driven API use in the call rate - Use a slow-period response time, not the best case - Add exponential backoff with jitter on retries - Spread scheduled jobs across the hour instead of starting them together **Cta:** If your integrations keep hitting limits, Netray can review the call patterns and script performance and help redesign the flow with batching and queues. **Faq:** #### What is the NetSuite concurrency limit? **Answer:** It is the number of requests your account can process at the same time across supported web service types. The value depends on your service tier and any SuiteCloud Plus licences, so read it from your own account rather than assuming a default. #### What happens when I exceed the limit? **Answer:** Excess requests are rejected with a concurrency error, typically surfaced as an HTTP 429 on REST or a concurrency fault on SOAP. Your client must retry with backoff or the data does not arrive. #### Does a faster script really help? **Answer:** Yes. Concurrency is call rate multiplied by duration. Halving the response time halves the concurrent requests at the same call rate, which often costs less than buying more concurrency. #### Should I plan for the peak or the average? **Answer:** Plan for the peak. Errors occur when many calls overlap, so the peak multiplier matters more than the daily average. Measure your busiest minute and use that ratio. ## Search terms netsuite concurrency limit, netsuite 429 concurrent request limit exceeded, netsuite api concurrency calculator, netsuite integration throughput, netsuite restlet concurrency, netsuite suitecloud plus license concurrency, netsuite rate limit planning --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json