How many concurrent requests are allowed by IBMs API servers when using the OAuth method for authentication?
Resolving the problem
Concurrent requests and API servers when using OAuth.
By default, up to 10 concurrent requests are allowed to our API servers at any given time when using the OAuth method for authentication. OAuth Access Tokens allow calls to re-use existing tokens if they are still valid (within the 4 hour expiration window) so that a new token does not have to be generated with every call if an existing one is still valid. This will allow multiple mobile users to access data over a single token for example, when there are many simultaneous calls from a Mobile app.
If necessary, we recommend that you obtain a new Access Token every 3 hours to avoid the likelihood of losing access to the API.
Concurrent requests are not equal to access tokens. An example of concurrent requests would be hitting IBMÂ®’s servers with 99 RawRecipient calls at the same time and we won’t allow it. Once you get a response back from our servers, that single concurrent request is over and you’re back to being allowed 10. We will reject any request that needs to make use of an >= 11th request thread; we do not ‘hold’ the request and retry when a thread becomes available. This concurrency limit is per Org, not user, list, API request type, etc.
For mobile app use cases, if needed as multiple app users could perform an action in an app and hit our servers concurrently, you can make a request through the Client Support Team to raise the limit of concurrent requests.
Organizations and there is a per organization limit.