Integration Concurrency Limits & Governance

NetSuite enforces concurrency limits on the number of simultaneous requests an account can make. These limits are determined by the service tier and the number of SuiteCloud Plus (SC+) licenses purchased. For example, a base account in Service Tier 1 has a limit of 15 concurrent requests, which increases by 10 for each additional SC+ license. These limits regulate the simultaneous requests an account can make via web services (SOAP, RESTlets, SuiteTalk, and REST web services), helping maintain system stability and prevent excessive resource consumption.

Understanding Concurrency Limits in NetSuite

Concurrency limits in NetSuite are determined by:

  • Service tier (the NetSuite account type)
  • SuiteCloud Plus (SC+) licenses (additional licenses increase limits)
  • Authentication method used

When a NetSuite account exceeds its allowed concurrent requests, additional requests are throttled and receive a 429 – Request Limit Exceeded error.

Default Concurrency Limits

Service Tier – Concurrent Request Limit

Tier 1 (Base) – 15 concurrent requests

Tier 2 – 25 concurrent requests

Tier 3 – 35 concurrent requests

Tier 4 – 45 concurrent requests

Tier 5 – 55 concurrent requests

Impact of SuiteCloud Plus (SC+) Licenses

Each additional SC+ license increases the concurrency limit by 10 requests.

For example, if you have Tier 1 with two SC+ licenses, the new limit will be:

15 (base) + 10 (SC+) + 10 (SC+) = 35 concurrent requests.

Concurrency Limits by Integration Type

A. REST and SOAP Web Services

  • Share the same concurrency pool.
  • Respect the account-wide concurrency limit (based on tier and SC+ licenses).
  • Use token-based authentication (TBA) or basic authentication.

B. RESTlets

  • Per-user concurrency limit: 5 concurrent requests per user.
  • Account-wide concurrency still applies.
  • If multiple users call the same RESTlet, each user has 5 concurrent requests.

C. SuiteTalk (SOAP API)

  • SuiteTalk web services share the same global concurrency limit as REST.
  • Batch processing and large data extractions should be optimized to avoid concurrency issues.

D. Map/Reduce and Scheduled Scripts

  • Do not count toward concurrency limits unless they call web services.
  • RESTlets within these scripts count towards user-based limits.

Managing and Avoiding Concurrency Errors

Best Practices to Prevent 429 – Request Limit Exceeded

A. Distribute Requests Evenly

  • Implement request throttling or retry mechanisms with exponential backoff.
  • Avoid burst processing by spreading API calls over time.

B. Use Queues for High-Traffic Integrations

  • Implement a message queue system (e.g., AWS SQS, RabbitMQ) to control request flow.
  • Prioritize critical transactions and defer non-essential calls.

C. Leverage Map/Reduce Scripts

  • Break large data processing into smaller batch jobs instead of sending bulk API requests.

D. Monitor API Usage

  • Use NetSuite’s Concurrency Monitoring Dashboard (Setup > Integration > Integration Governance) to track real-time usage.
  • Set up alerts for nearing concurrency limits.

E. Token-Based Authentication (TBA)

  • NetSuite prioritizes TBA over basic authentication for web services.
  • Avoid using a single user for all integrations—distribute API requests across multiple users.

F. Upgrade to Higher Service Tiers

  • If you frequently hit concurrency limits, consider purchasing SC+ licenses or upgrading your service tier.

Conclusion

  • NetSuite enforces strict concurrency limits based on account tier and SC+ licenses.
  • RESTlets have a per-user limit of 5 concurrent calls.
  • Exceeding limits results in 429 errors—use retry logic and request throttling.
  • Monitor concurrency usage and optimize integrations with queues and batch processing.

By understanding these limitations and optimizing API usage, you can ensure seamless NetSuite integrations without hitting governance restrictions. For expert help with seamless integrations, contact Katoomi today. Our team will ensure worry-free integration with all your 3rd-party platforms.