Hi @Jenny Johnson, yes, the API limits the number of concurrent requests, but at the moment the configured limits are nominal only. We will be limiting both the number of requests per user, as well as a total limit for all API requests as a whole. This allows us to ensure a single user does not negatively impact the experience of others, as well as that all API requests being processed do not negatively impact the experience of WC1 users within the web application.
Hi @Shweta Lal - I have a follow up question to this. We have a prospect who would be interested in integrating WC1 API with multiple end systems (about 20 different systems) - I assume they can all use the same API key for sending requests? Are there any issues with concurrent requests from multiple systems? They may also have multiple groups set up within the same profile (one for each end system)
The API keys identify the API user and can be sent from different sources, however the number of concurrent requests is by user account, so if 20 systems are all using the same API user account, then there's a good chance more than 10 concurrent requests will be active and one or more of the systems will receive the 429 return status.
The API client is making too many concurrent requests, and some are being throttled. Throttled requests can be retried (with an updated request Date and HTTP signature) after a short delay.