Skip to main content
Solved

Concurrent API Requests

  • March 21, 2024
  • 1 reply
  • 258 views

aaldrich
Freshman II

We’ve been working on an integration to Acumatica utilizing a mixture of Web Service APIs and OData queries. After some testing we seem to be running into some issues with concurrency. We seem to hit our limit of 6. This seems unusable considering if we have 10 people view an item on the site the first 6 api calls would succeed but the other 4 will have to wait.

  1. Is there a way to get more concurrent requests with this license? e.g. would having multiple api users increase concurrency?
  2. Do OData calls count towards the limit?
  3. How hard/how expensive for our clients to get a license with 1000+ concurrency? or is that something Acumatica even offers

Best answer by ckwiat46

@aaldrich i’m not sure if you ever got a response to this, but we have a similar use case. If i understand your situation, you are bumping into api user limits for your license, correct? Assuming yes, i can’t speak to the license part, but if you were ok with dedicating one of your api logins to this application, then you can create a proxy endpoint that handles all of the requests from your custom application to acumatica. And this proxy would utilize one login through token access, etc. The downside of this approach is that Acumatica would see every request as from the same api login, therefore losing any security/access role rules you may have in place for each user. But depending on your use case, that may be acceptable. If you want to discuss further, just reply, and i would be happy to share more detail as to our implementation. 

View original
Did this topic help you find an answer to your question?

1 reply

Forum|alt.badge.img
  • Jr Varsity III
  • 44 replies
  • Answer
  • December 12, 2024

@aaldrich i’m not sure if you ever got a response to this, but we have a similar use case. If i understand your situation, you are bumping into api user limits for your license, correct? Assuming yes, i can’t speak to the license part, but if you were ok with dedicating one of your api logins to this application, then you can create a proxy endpoint that handles all of the requests from your custom application to acumatica. And this proxy would utilize one login through token access, etc. The downside of this approach is that Acumatica would see every request as from the same api login, therefore losing any security/access role rules you may have in place for each user. But depending on your use case, that may be acceptable. If you want to discuss further, just reply, and i would be happy to share more detail as to our implementation. 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings